| From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: BF member drongo doesn't like 035_standby_logical_decoding.pl |
| Date: | 2025-02-10 14:47:30 |
| Message-ID: | Z6oRgmD8m7zBo732@ip-10-97-1-34.eu-west-3.compute.internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junwang Zhao | 2025-02-10 15:00:05 | Re: SQL Property Graph Queries (SQL/PGQ) |
| Previous Message | David G. Johnston | 2025-02-10 14:46:15 | Re: Doc: Move standalone backup section, mention -X argument |