| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pavel(dot)tyslacki(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently |
| Date: | 2026-01-09 16:19:35 |
| Message-ID: | aWEql8SwVYIO9k72@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Dec 29, 2025 at 12:28:07PM -0500, Tom Lane wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
>> In postgres 18, I started getting random errors from `pg_dump`:
>> pg_dump: error: query failed: ERROR: could not open relation with OID 16741
>> pg_dump: detail: Query was: SELECT seqrelid, format_type(seqtypid, NULL),
>> seqstart, seqincrement, seqmax, seqmin, seqcache, seqcycle, last_value,
>> is_called FROM pg_catalog.pg_sequence, pg_get_sequence_data(seqrelid) ORDER
>> BY seqrelid;
>
> Thanks for the report. I posted an analysis here:
>
> https://www.postgresql.org/message-id/2885944.1767029161%40sss.pgh.pa.us
I've committed the following in an attempt to fix this:
https://postgr.es/c/7a485bd641 (master)
https://postgr.es/c/39d5555766 (v18)
Could you please verify that it fixes your use-case?
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paveł Tyślacki | 2026-01-09 22:56:38 | Re: BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently |
| Previous Message | PG Bug reporting form | 2026-01-09 10:14:28 | BUG #19373: One backend hanging in AioIoUringExecution blocking other backends |