Re: pgsql: Fix restore of not-null constraints with inheritance - Mailing list pgsql-committers

From Alvaro Herrera
Subject Re: pgsql: Fix restore of not-null constraints with inheritance
Date
Msg-id 202404181408.kqlwnqwshxtr@alvherre.pgsql
Whole thread Raw
In response to pgsql: Fix restore of not-null constraints with inheritance  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-committers
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/



pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: docs: Mention that pg_combinebackup does not verify backups.
Next
From: Alvaro Herrera
Date:
Subject: pgsql: Don't try to assign smart names to constraints