Re: Logical replication timeout problem - Mailing list pgsql-hackers

From Gregory Stark (as CFM)
Subject Re: Logical replication timeout problem
Date
Msg-id CAM-w4HNSaMyC1NxaX+JkBWkP8ArLAKf3+k1=ZxELxNqiU7DWXg@mail.gmail.com
Whole thread Raw
In response to Re: Logical replication timeout problem  (Andres Freund <andres@anarazel.de>)
Responses RE: Logical replication timeout problem  ("wangw.fnst@fujitsu.com" <wangw.fnst@fujitsu.com>)
List pgsql-hackers
On Wed, 8 Feb 2023 at 15:04, Andres Freund <andres@anarazel.de> wrote:
>
> Attached is a current, quite rough, prototype. It addresses some of the points
> raised, but far from all. There's also several XXXs/FIXMEs in it.  I changed
> the file-ending to .txt to avoid hijacking the CF entry.

It looks like this patch has received quite a generous helping of
feedback from Andres. I'm setting it to Waiting on Author.

On the one hand it looks like there's a lot of work to do on this but
on the other hand it sounds like this is a live problem in the field
so if it can get done in time for release that would be great but if
not then feel free to move it to the next commitfest (which means next
release).


-- 
Gregory Stark
As Commitfest Manager



pgsql-hackers by date:

Previous
From: Andrei Zubkov
Date:
Subject: Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements
Next
From: Nathan Bossart
Date:
Subject: Re: Making empty Bitmapsets always be NULL