Re: serializable master and non-serializable hot standby: feasible set up?

On Tue, 2024-10-15 at 16:27 -0700, Jacob Biesinger wrote: > *would you* expect to be able to stand up a `repeatable read` replica against > a > `serializable` master? My expectation is that you'd simply change the setting > in > a .conf file on the replica and be good to go; is there something th

RE: serializable master and non-serializable hot standby: feasible set up?

Just out of curiosity, what's the use case for this? Clay Jackson Database Solutions Sales Engineer [cid:image001.jpg@01DB1F41.568B8100] clay.jack...@quest.com office 949-754-1203 mobile 425-802-9603

serializable master and non-serializable hot standby: feasible set up?

Howdy! I've been going back and forth with the GCP CloudSQL engineering team about the feasibility of a particular setup, and I'm pinging the list here hoping for a sanity check. They assure me that it's impossible and I think they must be mistaken, but I have limited experience administrating my

Re: Questions about document "Concurrenry control" section

On 2024-10-12 09:02:37 -0700, Adrian Klaver wrote: > On 10/12/24 03:17, Peter J. Holzer wrote: > > On 2024-10-11 21:21:16 -0700, Adrian Klaver wrote: > > > On 10/11/24 20:10, admin@iseki.space wrote: > > > > I found. Maybe we should reply to the mailing list only. Otherwise we'll > > > > receive mu

Re: how to know if the sql will run a seq scan

On 10/15/24 13:50, Vijaykumar Jain wrote: Sorry top posting, coz Gmail app on phone. Yeah, my point was for example we have a large table and we are attaching a table as a partition. Now it will scan the whole table to validate the constraint and that will create all sorts of problems. Now y

Re: how to know if the sql will run a seq scan

Sorry top posting, coz Gmail app on phone. Yeah, my point was for example we have a large table and we are attaching a table as a partition. Now it will scan the whole table to validate the constraint and that will create all sorts of problems. I understand the benefit of not valid constraint and

Re: how to know if the sql will run a seq scan

On 10/15/24 12:50, Vijaykumar Jain wrote: Hi, tl;dr I am trying to learn what sql can result in a full seq scan. Basically there is a lot of info on the internet of what ddl change may take an access exclusive lock while running a seq scan and hold for long.  And for some cases we can make

how to know if the sql will run a seq scan

Hi, tl;dr I am trying to learn what sql can result in a full seq scan. Basically there is a lot of info on the internet of what ddl change may take an access exclusive lock while running a seq scan and hold for long. And for some cases we can make use of "not valid" constraint and then run a val

Re: Advice on efficiently logging outputs to PostgreSQL

> On Oct 15, 2024, at 07:17, Dominique Devienne wrote: > Am I worrying too much? :) Probably. :-) The main things I'd worry about is: 1. What's the ratio of log lines to database updates? You want this to be as high as usefully possible, since in effect you are doing write amplification by

WAL replication standby server: query

List , I am trying to configure a WAL replicated standby server(EDB16) .. In the archive command I used a dedicated "/data/archive " directory for WAL archiving as follows, as I don't want any WAL overwriting in the default WAL directory and loss of WAL files. I have archive_command= ' c

Advice on efficiently logging outputs to PostgreSQL

I have an existing heavy ETL that serially loads tons of data to PostgreSQL. This is done using a CLI tool, processing one project after another. I'd like to parallelize / distribute the work, which I could do from my CLI tool, but 1) that would be confined to a single machine, and 2) we'd like to

Re: Inefficient use of index scan on 2nd column of composite index during concurrent activity

On Tue, 15 Oct, 2024, 15:15 David Rowley, wrote: > On Sat, 12 Oct 2024 at 02:28, Durgamahesh Manne > wrote: > > Second column of composite index not in use effectively with index scan > when using second column at where clause > > > > I have composite index on (placedon,id) of test > > When quer

Re: Inefficient use of index scan on 2nd column of composite index during concurrent activity

On Sat, 12 Oct 2024 at 02:28, Durgamahesh Manne wrote: > Second column of composite index not in use effectively with index scan when > using second column at where clause > > I have composite index on (placedon,id) of test > When quering select * from test where id = '4234'; > Value of id chan