| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Fix restore of not-null constraints with inheritance |
| Date: | 2024-04-18 14:08:58 |
| Message-ID: | 202404181408.kqlwnqwshxtr@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2024-04-18 14:30:15 | pgsql: Don't try to assign smart names to constraints |
| Previous Message | Robert Haas | 2024-04-18 13:55:49 | pgsql: docs: Mention that pg_combinebackup does not verify backups. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-04-18 14:50:10 | Re: pg_combinebackup does not detect missing files |
| Previous Message | Alvaro Herrera | 2024-04-18 13:41:28 | Re: pg17 issues with not-null contraints |