Date: Tue, 6 Feb 2024 10:53:43 -0600
From: Nathan Bossart <nathandbossart@gmail.com>
To: Michael Banck <mbanck@gmx.net>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
	pgsql-hackers@lists.postgresql.org
Subject: Re: Set log_lock_waits=on by default
Message-ID: <20240206165343.GA3841415@nathanxps13>
References: <b8b8502915e50f44deb111bc0b43a99e2733e117.camel@cybertec.at>
 <659ffa38.170a0220.eea6a.28fc@mx.google.com>
 <65b146b9.170a0220.c645b.0891@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <65b146b9.170a0220.c645b.0891@mx.google.com>
Archived-At: 
 <https://www.postgresql.org/message-id/20240206165343.GA3841415%40nathanxps13>
Precedence: bulk

I saw this was marked ready-for-committer, so I took a look at the thread.
It looks like there are two ideas:

* Separate log_lock_waits from deadlock_timeout.  It looks like this idea
  has a decent amount of support, but I didn't see any patch for it so far.
  IMHO this is arguably a prerequisite for setting log_lock_waits on by
  default, as we could then easily set it higher by default to help address
  concerns about introducing too much noise in the logs.

* Set log_lock_waits on by default.  The folks on this thread seem to
  support this idea, but given the lively discussion for enabling
  log_checkpoints by default [0], I'm hesitant to commit something like
  this without further community discussion.

[0] https://postgr.es/m/CALj2ACX-rW_OeDcp4gqrFUAkf1f50Fnh138dmkd0JkvCNQRKGA%40mail.gmail.com

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com