Date: Fri, 9 Jan 2026 10:19:35 -0600
From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pavel.tyslacki@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19365: postgres 18 pg_dump fails whan drop sequence
 concurrently
Message-ID: <aWEql8SwVYIO9k72@nathan>
References: <19365-6245240d8b926327@postgresql.org>
 <2886168.1767029287@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2886168.1767029287@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/aWEql8SwVYIO9k72%40nathan>
Precedence: bulk

On Mon, Dec 29, 2025 at 12:28:07PM -0500, Tom Lane wrote:
> PG Bug reporting form <noreply@postgresql.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