Re: Postgres 17 domains with NOT NULL and pg_get_constraintdef() - Mailing list pgsql-general

From shammat@gmx.net
Subject Re: Postgres 17 domains with NOT NULL and pg_get_constraintdef()
Date
Msg-id 46650e9e-beb3-46ad-a26a-b356d6476cd2@gmx.net
Whole thread Raw
In response to Re: Postgres 17 domains with NOT NULL and pg_get_constraintdef()  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-general
Am 08.01.25 um 14:10 schrieb Alvaro Herrera:
>> However, because the domain is defined with NOT NULL, this fails with
>>
>>> ERROR: invalid constraint type "n"
>>
>> with 17.2 on Windows and Linux.
>>
>> This is a result of storing the NOT NULL constraint in pg_constraint
>> and can easily be avoided by either using contype <> 'n' or by not calling
>> pg_get_constraintdef if contype = 'n'
>
> Yeah, thanks for the report -- this is clearly a bug and it was fixed
> already in the 17 branch, but it's not been released yet.  It'll be in
> the February release.

Thanks for the confirmation.





pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Unexpected results from a query with UNION ALL
Next
From: Ron Johnson
Date:
Subject: INTERVAL MINUTE TO SECOND didn't do what I thought it would do