| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> | 
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: Catalog domain not-null constraints | 
| Date: | 2023-11-28 19:43:54 | 
| Message-ID: | 96cefb54-61e5-45d8-b94b-da57fc1b1b92@eisentraut.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On 23.11.23 14:13, Aleksander Alekseev wrote:
> =# create domain connotnull1 integer;
> =# create domain connotnull2 integer;
> =# alter domain connotnull1 add not null value;
> =# alter domain connotnull2 set not null;
> =# \dD
> ERROR:  unexpected null value in cached tuple for catalog
> pg_constraint column conkey
Yeah, for domain not-null constraints pg_constraint.conkey is indeed 
null.  Should we put something in there?
Attached is an updated patch that avoids the error by taking a separate 
code path for domain constraints in ruleutils.c.  But maybe there is 
another way to arrange this.
| Attachment | Content-Type | Size | 
|---|---|---|
| v2-0002-Catalog-domain-not-null-constraints.patch | text/plain | 25.1 KB | 
| v2-0001-Add-tests-for-domain-related-information-schema-v.patch | text/plain | 7.2 KB | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2023-11-28 20:27:39 | Re: Testing autovacuum wraparound (including failsafe) | 
| Previous Message | David Rowley | 2023-11-28 19:40:02 | Re: Memory consumed by paths during partitionwise join planning |