From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Tender Wang <tndrwang(at)gmail(dot)com> |
Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Can't find not null constraint, but \d+ shows that |
Date: | 2024-04-10 17:23:25 |
Message-ID: | 202404101723.4ag5z2mbgmsl@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2024-Apr-10, Alvaro Herrera wrote:
> One thing missing here is pg_dump support. If you just dump this table,
> it'll end up with no constraint at all. That's obviously bad, so I
> propose we have pg_dump add a regular NOT NULL constraint for those, to
> avoid perpetuating the weird situation further.
Here's another crude patchset, this time including the pg_dump aspect.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"On the other flipper, one wrong move and we're Fatal Exceptions"
(T.U.X.: Term Unit X - http://www.thelinuxreview.com/TUX/)
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Handle-ALTER-.-DROP-NOT-NULL-when-no-pg_constrain.patch | text/x-diff | 9.7 KB |
v2-0002-support-this-in-pg_dump.patch | text/x-diff | 3.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2024-04-10 17:25:20 | Re: Table AM Interface Enhancements |
Previous Message | Dmitry Koval | 2024-04-10 17:22:35 | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |