Re: Set log_lock_waits=on by default
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Michael Banck <mbanck@gmx.net>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Nathan Bossart <nathandbossart@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-04-08T14:32:49Z
Lists: pgsql-hackers
On Fri, 2024-07-19 at 11:54 +0200, Laurenz Albe wrote: > On Thu, 2024-07-18 at 12:25 +0200, Michael Banck wrote: > > this patch is still on the table, though for v18 now. > > > > Nathan mentioned up-thread that he was hesitant to commit this without > > further discussion. Laurenz, Stephen and I are +1 on this, but when it > > comes to committers having chimed in only Tom did so far and was -1. > > > > Are there any others who have an opinion on this? > > If we want to tally up, there were also +1 votes from Christoph Berg, > Shinya Kato, Nikolay Samokhvalov, Jeremy Schneider and Frédéric Yhuel. > > The major criticism is Tom's that it might unduly increase the log volume. > > I'm not trying to rush things, but I see little point in kicking a trivial > patch like this through many commitfests. If no committer wants to step > up and commit this, it should be rejected. Well, it didn't make v18. But this patch got enough votes in favor that I am not going to withdraw it. Yours, Laurenz Albe
Commits
-
Default to log_lock_waits=on
- 2aac62be8cbb 19 (unreleased) landed
-
Generate GUC tables from .dat file
- 63599896545c 19 (unreleased) cited