Date: Fri, 13 Feb 2026 15:00:18 -0600
From: Nathan Bossart <nathandbossart@gmail.com>
To: dominik.hirt@hub28.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19407: pg_dump : DROP RULE creates forward references
Message-ID: <aY-Q4met3RVF08LP@nathan>
References: <19407-0c327e0fc912b451@postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <19407-0c327e0fc912b451@postgresql.org>
Archived-At: <https://www.postgresql.org/message-id/aY-Q4met3RVF08LP%40nathan>
Precedence: bulk

On Fri, Feb 13, 2026 at 09:02:37AM +0000, PG Bug reporting form wrote:
> During dump / restore with pg_dump / psql, I encounter a dependency ordering
> issue that breaks the import when using ON_ERROR_STOP=on.
> 
> Problem: pg_dump executes DROP RULE for specific views, forcing them to be
> recreated before their dependencies (custom types, collations) exist in the
> dump file, causing import failures.

I think this is an even simpler reproducer:

	create type t as enum ('a', 'b');
	create table tt (a t primary key, b text);
	create view v as select * from tt group by a;

Commit d8c05aff56 [0] did some work in this area, but this issue may even
predate that.  In any case, it seems like pg_dump needs to create the type
before it creates the dummy view to deal with circular dependencies.

[0] https://postgr.es/m/flat/19092.1479325184%40sss.pgh.pa.us

-- 
nathan