Postgres Pro
Downloads
Home   >   mailing lists

Re: Set log_lock_waits=on by default - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Set log_lock_waits=on by default
Date
Msg-id 20240206165343.GA3841415@nathanxps13
Whole thread Raw
In response to Re: Set log_lock_waits=on by default  (Michael Banck <mbanck@gmx.net>)
Responses Re: Set log_lock_waits=on by default
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Reducing connection overhead in pg_upgrade compat check phase
Next
From: Nathan Bossart
Date:
Subject: Re: Reducing connection overhead in pg_upgrade compat check phase