Logical Replication Sync Validation

Greetings, We have the following setup: A pg10 cluster with logical replication to a pg15 cluster, set up with the following query: CREATE PUBLICATION "dbname_pub" FOR ALL TABLES; We do an initial sync of DDL with pg_dump. The purpose of the replication is to perform an online upgrade with mi

Re: Logical Replication Sync Validation

> On Apr 18, 2023, at 01:20, Robert Sjöblom wrote: > Another idea we've had would be to use CTID to fetch the last row > (update/insert) in each table on both sides and compare row content, is this > feasible? Is it safe to rely on CTIDs across logical replication? No. CTIDs aren't sent ove

Re: Guidance on INSERT RETURNING order

Sorry, I may have jumped to a conclusion that's not quite correct. On Mon, 17 Apr 2023 at 23:58, Federico wrote: > On Tue, 18 Apr 2023 at 00:21, John Howroyd > wrote: > > ... > > > > Personally, I didn't see Frederico's comment as anything to do with > order; just how one could output additiona

Re: Logical Replication Sync Validation

> On Apr 18, 2023, at 03:45, Robert Sjöblom wrote: > I'm aware of that. But you can, however, do something like: > > SELECT * FROM FOO WHERE CTID = (SELECT MAX(CTID) FROM FOO); > > on both sides. The idea being that if I change FOO, the CTID of the changed > row will not be the same on both

Re: Request for information about postgres version 15.2 stability

On 4/17/23 23:56, gayathri ramesh wrote: Hi Team, Our company is currently supporting around 100+ postgres databases and we are planning to upgrade to version 15.2. We want to ensure that there are no major critical bugs that could impact our production systems. I would appreciate if you cou

Re: Question on SSI - Serializable Snapshot Isolation

ok thanks tom. On Mon, Apr 17, 2023 at 2:39 PM Tom Lane wrote: > Siddharth Jain writes: > > When using SSI , lets say we have > two > > transactions T1 and T2 and there is a serialization conflict. Postgres > > knows when one or the other transaction is doo

Re: Request for information about postgres version 15.2 stability

On Tue, 2023-04-18 at 12:26 +0530, gayathri ramesh wrote: > Our company is currently supporting around 100+ postgres databases and we are > planning > to upgrade to version 15.2. We want to ensure that there are no major > critical bugs > that could impact our production systems. > > I would app

Postgres as a LRU cache?

Has anyone tried using Postgres as a LRU cache for data in cloud blob storage? I have a lot of data in Cassandra and want to move that to Backblaze (like S3 but cheaper and less available). Cassandra is working well but I have to add new nodes more frequently that I would like. The older data is ra

Re: Logical Replication Sync Validation

On Tue, 2023-04-18 at 10:20 +0200, Robert Sjöblom wrote: > At the moment where we would switch to pg15 being the primary/lead we > will stop writes to pg10; at that point we will validate that we are > fully in sync, tear down pg10 and send writes to pg15. Our question is > how we can validate o

Re: Request for information about postgres version 15.2 stability

Laurenz Albe writes: > We don't have any information about yet undiscovered PostgreSQL bugs. Indeed. > We believe that PostgreSQL 15.2 is a great and stable database, but we are > biased. One moderately objective way to see how stable a release branch is is to count how many commits fix bugs i

ETCD for Patroni configuration error

Hi Team, I am in configuring etcd cluster, and facing below error while I start etcd or see member list. 2023-04-19 11:31:31.001071 N | embed: serving insecure client requests on xxx.xx.xx.xx:2379, this is strongly discouraged! 2023-04-19 11:31:31.001184 N | embed: serving insecure client reque