From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix restore of not-null constraints with inheritance
Date: Thu, 18 Apr 2024 16:08:58 +0200
Message-ID: <202404181408.kqlwnqwshxtr@alvherre.pgsql> (raw)
In-Reply-To: <E1rxRxO-002hM4-Lk@gemulon.postgresql.org>
On 2024-Apr-18, Alvaro Herrera wrote:
> Lastly, make two changes to pg_dump: 1) do not try to drop a not-null
> constraint that's marked as inherited; this allows a dump to restore
> with no errors if a table with a PK inherits from another which also has
> a PK; 2) avoid giving inherited constraints throwaway names, for the
> rare cases where such a constraint survives after the restore.
Hmm, this last bit broke pg_upgrade on crake. I'll revert this part,
meanwhile I'll be installing 9.2 to see if it can be fixed in a better way.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: alvherre@alvh.no-ip.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix restore of not-null constraints with inheritance
In-Reply-To: <202404181408.kqlwnqwshxtr@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox