| From: | Manu <manuelreyesbravo(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Kirill Reshke <reshkekirill(at)gmail(dot)com> |
| Subject: | Re: REPACK hits assertion failure on postmaster death exit |
| Date: | 2026-10-08 13:36:14 |
| Message-ID: | 179146657463.649934.13889200288210614704@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Álvaro,
> I think the real problem is the shutdown of pgaio or pgstats.
That matches what I saw, and it looks like both are involved. One
path is on the pgaio side: the abort reaches pgaio_io_wait (through
DropRelationsAllBuffers -> WaitIO) and waits on an IO that can never
complete, since the IO workers are gone with the postmaster -- with
io_method=sync that wait disappears, which is how I isolated it. The
pgstat report is the other: it runs with a transaction still active,
and merely clearing the pending list trades the assert for "releasing
ref with pending data".
Happy to test the repack.c variant you suggest, if that helps.
Regards,
Manu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2026-10-08 13:42:09 | Re: [PG19] COPY (query) TO ... (FORMAT json) uses the table's column names |
| Previous Message | Andrei Lepikhov | 2026-10-08 13:35:43 | Re: hashjoins vs. Bloom filters (yet again) |