| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alexey Bashtanov <bashtanov(at)imap(dot)cc>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: should all not-null constraints be inherited? |
| Date: | 2021-03-31 17:40:37 |
| Message-ID: | 20210331174037.GA344@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2021-Mar-31, Tom Lane wrote:
> Yeah, that's been on the to-do list for a long time. The current
> theory about it is that NOT NULL constraints ought to be represented
> as entries in pg_constraint like CHECKs are, so that the inheritance
> count and so forth could be managed the same way. We could keep
> attnotnull for convenience but it'd just mirror the existence of
> the pg_constraint entry.
>
> IIRC Alvaro had a WIP patch for this, but I've not heard anything
> about it lately.
That one is the first thing on my list for the next cycle.
--
Álvaro Herrera Valdivia, Chile
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-03-31 20:06:01 | BUG #16951: pg_restore segfaults on custom format piped from a different version of PG |
| Previous Message | Tom Lane | 2021-03-31 17:02:01 | Re: should all not-null constraints be inherited? |