Horton

Re: Set log_lock_waits=on by default

Shinya Kato <shinya11.kato@gmail.com>

View thread
From: Shinya Kato <shinya11.kato@gmail.com>
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: 2025-09-04T05:12:25Z
Lists: pgsql-hackers 
Hi,

On Tue, Apr 8, 2025 at 11:33 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
> Well, it didn't make v18.
>
> But this patch got enough votes in favor that I am not going to withdraw it.

Thank you for discussing it.

diff --git a/src/backend/utils/misc/guc_tables.c
b/src/backend/utils/misc/guc_tables.c
index f7c9882f7c..1f3d56e6ee 100644
--- a/src/backend/utils/misc/guc_tables.c
+++ b/src/backend/utils/misc/guc_tables.c
@@ -1519,7 +1519,7 @@ struct config_bool ConfigureNamesBool[] =
  NULL
  },
  &log_lock_waits,
- false,
+ true,
  NULL, NULL, NULL
  },
  {

Due to 635998965 [0], you need to change guc_parameters.dat instead of
guc_tables.c.

[0] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=63599896545c7869f7dd28cd593e8b548983d613


--
Best regards,
Shinya Kato
NTT OSS Center