Re: BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently

I have a simple test `pg_get_sequence_data(0)` that works fine with patch,
concurrent pg_dump works fine for my case too.

Thanks
Pavel

On Fri, 9 Jan 2026 at 16:19, Nathan Bossart <nathandbossart(at)gmail(dot)com>
wrote:

> 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
>