From: Christoph Berg <myon@debian.org>
To: Jakub Wartak <jakub.wartak@enterprisedb.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Michael Banck <mbanck@gmx.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Nathan Bossart <nathandbossart@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Set log_lock_waits=on by default
Date: Tue, 3 Sep 2024 21:39:01 +0200
Message-ID: <Ztdl1R4RuRsmlUTO@msg.df7cb.de> (raw)
In-Reply-To: <CAKZiRmz4k_-4H=5R0z1sbj-jgQOKukNwv7DpPtd0qcpLjRgaOg@mail.gmail.com>
References: <65b146b9.170a0220.c645b.0891@mx.google.com>
<20240206165343.GA3841415@nathanxps13>
<524751.1707240550@sss.pgh.pa.us>
<6698edb4.5d0a0220.df6fa.5b59@mx.google.com>
<5dc4e037f60467da7bf7d17b10f6ec632a7c9095.camel@cybertec.at>
<ZpppCLK1gNs7aXQS@msg.df7cb.de>
<CA+TgmoYTOQk8M7Zpg2p8xuSK6SiRQD7mC_5SH9y5qVghqB4tWg@mail.gmail.com>
<Zpp2pYnZ5fYvtymC@msg.df7cb.de>
<CA+TgmoZw=uagLNBfji=3EW31yR6OL092=OXqi1FM0_doYSCSLw@mail.gmail.com>
<CAKZiRmz4k_-4H=5R0z1sbj-jgQOKukNwv7DpPtd0qcpLjRgaOg@mail.gmail.com>
Re: Jakub Wartak
> 1. dev/testing DBs: where frankly speaking nobody cares about such DBs
> until they stop/crash; this also includes DBs from new users on dev
> laptops too
> 2. production systems: where it matters to have log_lock_waits=on (and
> people may start getting nervous if they don't have it when the issue
> strikes)
> 3. PG on embedded hardware, where it would be worth to be actually
> disabled and not consume scare resources
>
> I would like to +1 too to the default value of log_lock_waits=on due
> to mostly working nearby use case #2, and because due to my surprise,
> we had __ 74.7% __ of individual installations having it already as
> 'on' already within last year support reports here at EDB (that may be
> biased just to class of systems #2).
Ack. Thanks for that field data.
> But I could be easily convinced too, that it is the embedded space
> (#3) that has the biggest amount of default installations, so we
> should stick log_lock_waits=off by default. However, I believe that
> such specialized use of PG already might require some "customizations"
> first to even further reduce e.g shared_buffers, right?
The ship "no log spam by default" has definitely sailed since
log_checkpoints defaults to 'on'.
> I would also like to believe that if people try to use PostgreSQL for
> the first time (use case #1), they would be much better served when
> the log would contain info about stuck sessions.
Definitely.
Christoph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers@postgresql.org
Cc: myon@debian.org, jakub.wartak@enterprisedb.com, robertmhaas@gmail.com, laurenz.albe@cybertec.at, mbanck@gmx.net, tgl@sss.pgh.pa.us, nathandbossart@gmail.com
Subject: Re: Set log_lock_waits=on by default
In-Reply-To: <Ztdl1R4RuRsmlUTO@msg.df7cb.de>
References: <65b146b9.170a0220.c645b.0891@mx.google.com> <20240206165343.GA3841415@nathanxps13> <524751.1707240550@sss.pgh.pa.us> <6698edb4.5d0a0220.df6fa.5b59@mx.google.com> <5dc4e037f60467da7bf7d17b10f6ec632a7c9095.camel@cybertec.at> <ZpppCLK1gNs7aXQS@msg.df7cb.de> <CA+TgmoYTOQk8M7Zpg2p8xuSK6SiRQD7mC_5SH9y5qVghqB4tWg@mail.gmail.com> <Zpp2pYnZ5fYvtymC@msg.df7cb.de> <CA+TgmoZw=uagLNBfji=3EW31yR6OL092=OXqi1FM0_doYSCSLw@mail.gmail.com> <CAKZiRmz4k_-4H=5R0z1sbj-jgQOKukNwv7DpPtd0qcpLjRgaOg@mail.gmail.com> <Ztdl1R4RuRsmlUTO@msg.df7cb.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox