Re: Command order bug in pg_dump - Mailing list pgsql-bugs

From Kirill Reshke
Subject Re: Command order bug in pg_dump
Date
Msg-id CALdSSPi1g93=+q_0dibiwNr095Rj14MWEhF=QeUZNxKPaOp1xw@mail.gmail.com
Whole thread Raw
In response to Re: Command order bug in pg_dump  (Kirill Reshke <reshkekirill@gmail.com>)
List pgsql-bugs
On Mon, 21 Apr 2025 at 22:30, Kirill Reshke <reshkekirill@gmail.com> wrote:
>
> My view of this problem is that pg_dump fails its purpose (to produce
> restorable dump) because... Lack of control? What if we can force
> inherited child constraint names?
> So, along with AT ADD CONSTRAINT, we can provide a list of names and
> say: instead of using a constraint name generation rule, the server
> should choose these names in order.

Forget this nonsense, this is a bad idea.

-- 
Best regards,
Kirill Reshke



pgsql-bugs by date:

Previous
From: Kirill Reshke
Date:
Subject: Re: Command order bug in pg_dump
Next
From: Alvaro Herrera
Date:
Subject: Re: Command order bug in pg_dump