Re: Memory context can be its own parent and child in replication command

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Memory context can be its own parent and child in replication command
Date: 2025-04-20 19:28:51
Message-ID: 442863.1745177331@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> ... An obvious candidate is subscription/t/100_bugs.pl, but
> the test failed there for lack of access to the test_decoding plugin.
> Perhaps we could use another plugin, but I didn't try hard.

Ah, I realized we could just use pgoutput, since the test doesn't
actually do anything that would exercise the plugin. So here's
a v4 with the test restored.

regards, tom lane

Attachment Content-Type Size
v4-0001-Use-the-same-cmd_context-throughout-a-walsender-s.patch text/x-diff 5.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2025-04-20 21:53:39 Re: Back-patch of: avoid multiple hard links to same WAL file after a crash
Previous Message Tom Lane 2025-04-20 18:18:27 Re: Memory context can be its own parent and child in replication command