Re: Set log_lock_waits=on by default
Christoph Berg <myon@debian.org>
From: Christoph Berg <myon@debian.org>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Michael Banck <mbanck@gmx.net>, Tom Lane <tgl@sss.pgh.pa.us>, Nathan Bossart <nathandbossart@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2024-07-19T13:24:24Z
Lists: pgsql-hackers
Re: Laurenz Albe > 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. That would be a pity, I still think log_lock_waits=on by default would be a good thing. I have not seen any server yet where normal, legitimate operation would routinely trigger the message. (If it did, people should likely have used SKIP LOCKED or NOWAIT instead.) It would only increase the log volume on systems that have a problem. Christoph
Commits
-
Default to log_lock_waits=on
- 2aac62be8cbb 19 (unreleased) landed
-
Generate GUC tables from .dat file
- 63599896545c 19 (unreleased) cited