| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: cataloguing NOT NULL constraints |
| Date: | 2023-07-24 17:18:54 |
| Message-ID: | 20230724171854.52b3lqi2jn4yvgxe@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-Jul-24, Alvaro Herrera wrote:
> That would die with "redundant NOT NULL declarations", but current
> master doesn't do that; and we don't do it for UNIQUE UNIQUE either.
> So I modified the patch to make it ignore the dupe and create a single
> constraint. This (and rebasing to current master) are the only changes
> in v15.
Did I forget the attachments once more? Yup, I did. Here they are.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
| Attachment | Content-Type | Size |
|---|---|---|
| v15-0001-Remember-PK-oid-for-partitioned-tables-even-when.patch | text/x-diff | 2.5 KB |
| v15-0002-Add-pg_constraint-rows-for-NOT-NULL-constraints.patch | text/x-diff | 225.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2023-07-24 17:19:48 | Re: cataloguing NOT NULL constraints |
| Previous Message | Alvaro Herrera | 2023-07-24 17:17:33 | Re: cataloguing NOT NULL constraints |