Re: Catalog domain not-null constraints

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com>
Subject: Re: Catalog domain not-null constraints
Date: 2024-03-18 07:46:28
Message-ID: b6123d6b-b94e-4e03-9e9c-dc7d292f3840@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Anyway, in order to move this forward, here is an updated patch where
the ADD CONSTRAINT ... NOT NULL behavior for domains matches the
idempotent behavior of tables. This uses the patch that Jian He posted.

Attachment Content-Type Size
v4-0001-Add-tests-for-domain-related-information-schema-v.patch text/plain 7.3 KB
v4-0002-Catalog-domain-not-null-constraints.patch text/plain 26.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Himanshu Upadhyaya 2024-03-18 07:56:59 Re: remaining sql/json patches
Previous Message Yugo NAGATA 2024-03-18 07:44:29 Re: pg_column_toast_chunk_id: a function to get a chunk ID of a TOASTed value