Re: Set log_lock_waits=on by default

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>
Cc: Michael Banck <mbanck(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Set log_lock_waits=on by default
Date: 2025-09-07 21:46:32
Message-ID: c69a6198a05f3e9d74d8240483cbc6dbbaacb86c.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2025-09-04 at 14:12 +0900, Shinya Kato wrote:
> Due to 635998965 [0], you need to change guc_parameters.dat instead of
> guc_tables.c.

Thanks for pointing that out to me!
Here is an updated patch.

Yours,
Laurenz Albe

Attachment Content-Type Size
v2-0001-Default-to-log_lock_waits-on.patch text/x-patch 3.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tender Wang 2025-09-08 00:51:39 Re: Reduce "Var IS [NOT] NULL" quals during constant folding
Previous Message Tom Lane 2025-09-07 21:36:32 Re: Conflict detection for update_deleted in logical replication