On Wed, Oct 21, 2026 at 6:09 AM shihao zhong <[email protected]> wrote: > > I agree. 19 gets a note in the docs, and v6 goes to master first. > > The docs patch for 19 is attached. It says what blocks, how to see the > PID, and how to get out. I am happy to change the wording. >
<para> + To avoid the wait, set <varname>wal_level</varname> to + <literal>logical</literal> on the standby. Will this help when the promotion is stuck? I feel this defeats the purpose of the feature introduced in commit 67c20979ce7. Also, not sure saying: " 15 minutes with default TCP settings" doesn't sound like a good idea because default on Windows may be different; additionally, if the client is alive but has stopped reading, it can take much more time. I have tried to make it generic in the attached (the patch is atop v20 for now). > For (2), I think it is still worth doing on master even with v6. It > would also cover replay of the enable record and recovery conflicts > with a backend stuck on a client write. Manu, do you want to post it? > If not, I am happy to take it. > If we anyway would like to implement killing of connections that didn't absorb barriers then do we even need v6. I am slightly hesitant about v6 because it adds more assumptions in the code like which processes can have stale cache. -- With Regards, Amit Kapila.
fix_doc.1.patch
Description: Binary data
