Hi, On Mon, Jan 27, 2025 at 07:13:01AM +0000, Bertrand Drouvot wrote: > On Fri, Jan 24, 2025 at 02:44:21PM -0500, Andres Freund wrote: > > If we could trigger VACUUM in a transaction on the primary this would be > > easy, but we can't. > > Another idea that I had ([1]) was to make use of injection points > around places where RUNNING_XACTS is emitted. IIRC I tried to work on this but > that was not simple as it sounds as we need the startup process not to be > blocked > .
I just proposed a patch to make use of an injection point to prevent the catalog_xmin of a logical slot to advance past the conflict point ([1]). That does not fix the issue on v16 though. [1]: https://www.postgresql.org/message-id/flat/Z6oQXc8LmiTLfwLA%40ip-10-97-1-34.eu-west-3.compute.internal Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
