Re: Optimize walsender handling invalid messages of 'drop publication' - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Optimize walsender handling invalid messages of 'drop publication'
Date
Msg-id 20230626211301.mj2p2zl3jpxmpfrw@awork3.anarazel.de
Whole thread Raw
In response to Re: Optimize walsender handling invalid messages of 'drop publication'  (Bowen Shi <zxwsbg12138@gmail.com>)
List pgsql-hackers
Hi,

On 2023-06-26 15:01:22 +0800, Bowen Shi wrote:
> This issue has been pending for several months without any response.
> And this problem still exists in the latest minor versions of PG 12
> and PG 13.
>
> I believe that the fix in this patch is helpful.
>
> The patch has been submitted
> https://commitfest.postgresql.org/43/4393/ .  Anyone who is interested
> in this issue can help with the review.

ISTM that the path for people encountering this issue is to upgrade.

It's not unheard of that we'd backpatch a performance improvements to the
backbranches, but it's pretty rare.  It's one thing to decide to backpatch an
optimization if it had time to "mature" in the development branch, but from
what I undestand you're proposing to apply this just to the back branches.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Add GUC to tune glibc's malloc implementation.
Next
From: Andres Freund
Date:
Subject: Re: Improve comment on cid mapping (was Re: Adding CommandID to heap xlog records)