| From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: Command order bug in pg_dump |
| Date: | 2025-04-21 17:33:44 |
| Message-ID: | CALdSSPi1g93=+q_0dibiwNr095Rj14MWEhF=QeUZNxKPaOp1xw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, 21 Apr 2025 at 22:30, Kirill Reshke <reshkekirill(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2025-04-21 17:44:27 | Re: Command order bug in pg_dump |
| Previous Message | Kirill Reshke | 2025-04-21 17:30:10 | Re: Command order bug in pg_dump |