Re: Set log_lock_waits=on by default

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 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-12 06:06:02
Message-ID: 1dc3a9cc-0f18-45a5-a575-74deeb362f59@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07.09.25 23:46, Laurenz Albe wrote:
> 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.

committed

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhang Mingli 2025-09-12 06:09:47 Re: Incremental View Maintenance, take 2
Previous Message Corey Huinker 2025-09-12 05:17:01 Re: Import Statistics in postgres_fdw before resorting to sampling.