public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alexander Lakhin <[email protected]>
To: Tom Lane <[email protected]>
To: Tomas Vondra <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: Iwata, Aya/岩田 彩 <[email protected]>
Cc: Peter Smith <[email protected]>
Cc: Kuroda, Hayato/黒田 隼人 <[email protected]>
Cc: Pavel Stehule <[email protected]>
Cc: Chao Li <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE
Date: Thu, 2 Apr 2026 07:00:00 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<TYRPR01MB12156CA129F54361D19ECAB56F541A@TYRPR01MB12156.jpnprd01.prod.outlook.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Hello Tom and Tomas,

01.04.2026 23:20, Tom Lane wrote:
> Alexander Lakhin<[email protected]> writes:
>> I think this can explain slow CommitTransactionCommand() and why it
>> happens not every time. Regarding other animals, I guess they can
>> experience the same bumps but not exceeding 5 seconds (50 tries). Thus,
>> from my understanding, for the failure to happen, we need to have slow
>> storage and initialize_worker_spi() -> CommitTransactionCommand() reaching
>> XLogFileClose().
> So, it remains not very clear why only widowbird is showing this
> failure, but I think we can safely take away the bottom-line
> conclusion that hard-wiring a maximum wait of 5s in
> CountOtherDBBackends() was not a great idea.

There also were two failures from jay: [1], [2], but yes, widowbird is
getting more and more consistent in that aspect: [3], probably because
of the storage (SD card?) degradation.

Tomas, maybe you could check if the write speed is more or less acceptable
there?

Regarding the test-specific fix, let me remind of the other failure from
widowbird: [4].

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jay&dt=2026-03-10%2019%3A26%3A19
[2] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jay&dt=2026-03-24%2020%3A43%3A24
[3] https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=widowbird&br=master
[4] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=widowbird&dt=2025-10-25%2010%3A35%3A03

Best regards,
Alexander

view thread (67+ messages)  latest in thread

reply

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox