Re: Command order bug in pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Kirill Reshke <reshkekirill(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Command order bug in pg_dump
Date: 2025-04-22 19:14:19
Message-ID: 1118297.1745349259@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera <alvherre(at)kurilemu(dot)de> writes:
> On 2025-Apr-21, Tom Lane wrote:
>> I experimented with the attached, which approximates "add some digits
>> to the name used for the parent constraint". (We could refactor
>> ChooseConstraintName if we wanted a less approximate version of that
>> rule, but I'm not sure it's worth the trouble.)

> This seems a better implementation of the idea than what I had in mind.
> For my part, please feel free to go ahead with this.

OK. I'll take a look first at whether the aforesaid refactoring
is easy enough to be worth doing.

> FWIW I've been migrating my main email address to a new domain. Finally
> got sick of noip.com.

Got it, thanks for the heads-up.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Shawn McCoy 2025-04-22 20:10:02 Re: Disabled logical replication origin session causes primary key errors
Previous Message Alvaro Herrera 2025-04-22 19:08:07 Re: Command order bug in pg_dump