Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #18027: Logical replication taking forever - Mailing list pgsql-bugs

From Amit Kapila
Subject Re: BUG #18027: Logical replication taking forever
Date
Msg-id CAA4eK1JMoa3GaNRGTafP2RznW50vV5snVF0+nhRo85uV9PwTkA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18027: Logical replication taking forever  (Andres Martin del Campo Campos <andres@invisible.email>)
Responses Re: BUG #18027: Logical replication taking forever
List pgsql-bugs
Tree view
On Thu, Jul 20, 2023 at 10:46 PM Andres Martin del Campo Campos <andres@invisible.email> wrote:
Seems like I don't have that table


 image.png


There are no errors in the logs but I only see dead tuples and no live tuples


oh, can you show us the dead and live tuple count on both publisher and subscriber? Ideally, COPY command should only copy the recent data based on the snapshot. It shouldn't copy the old/dead rows. One possibility I could think of is that due to some reason, if there is a failure during the initial sync process, it will ROLLBACK the whole copy and restart it again. So, that way one can see the table is growing with dead tuples and the copy is never finished especially if such an error occurs repeatedly. If that happens, you must see some error in the subscriber-side logs. Can you ensure in some way that such a phenomenon is not happening in your case?

--
With Regards,
Amit Kapila.
Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used
Next
From: Alexander Lakhin
Date:
Subject: Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker