Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1slZMu-008giw-QX for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Sep 2024 19:39:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1slZMt-00Fem3-SR for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Sep 2024 19:39:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1slZMt-00FelZ-AH for pgsql-hackers@lists.postgresql.org; Tue, 03 Sep 2024 19:39:11 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1slZMm-000Wem-Es for pgsql-hackers@lists.postgresql.org; Tue, 03 Sep 2024 19:39:09 +0000 Received: from msg.df7cb.de (unknown [IPv6:2a02:908:1470:d7a0:cdb3:ed:178:ed8b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 4Wywsy1vNRz3F2X; Tue, 3 Sep 2024 21:39:02 +0200 (CEST) Date: Tue, 3 Sep 2024 21:39:01 +0200 From: Christoph Berg To: Jakub Wartak Cc: Robert Haas , Laurenz Albe , Michael Banck , Tom Lane , Nathan Bossart , pgsql-hackers@lists.postgresql.org Subject: Re: Set log_lock_waits=on by default Message-ID: 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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