Horton

Re: Excessive number of replication slots for 12->14 logical replication

hubert depesz lubaczewski <depesz@depesz.com>

View thread View on postgr.es
From: hubert depesz lubaczewski <depesz@depesz.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Ajin Cherian <itsajin@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Peter Smith <smithpb2250@gmail.com>, "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2022-08-18T13:29:53Z
Lists: pgsql-bugs 
On Thu, Aug 18, 2022 at 04:00:29PM +0530, Amit Kapila wrote:
> Hubert, will you be able to verify if the proposed patch works in your
> exact scenario?

Not really, sorry, the environment in which I'm doing the tests is
pretty closed, and adding custom code would be virtually impossible.

Best regards,

depesz

Commits

  1. Make the tablesync worker's replication origin drop logic robust.

  2. Drop replication origin slots before tablesync worker exits.

  3. Allow multiple xacts during table sync in logical replication.