| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Subject: | Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?) |
| Date: | 2025-02-26 23:49:25 |
| Message-ID: | Z7-ohctRCTPxCon7@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 26, 2025 at 05:23:51PM -0500, Peter Geoghegan wrote:
> According to the revert commit's commit message there was also
> problems on batta at the time. Might have been the same issue that you
> saw on widowbird. Alexander?
This problem has already been discussed, and I saw the same backtrace
as you do on my hosts:
https://www.postgresql.org/message-id/Z7PSeT7AbrjmiCCV@paquier.xyz
It is not the first time where we have a problematic patch causing
some animals to freeze, so I would recommend using a wait_timeout =>
43200 or similar in the configuration of your buildfarm animals so as
they would unfreeze themselves without the need for a manual
intervention. This setting has saved me quite a few maintenance
cycles.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2025-02-27 00:08:59 | Re: Proposal: "query_work_mem" GUC, to distribute working memory to the query's individual operators |
| Previous Message | ahmedashour | 2025-02-26 23:23:07 | [PATCH] [52] Review of patch 5381 - Documentation for pgstatindex fragmentation |