Re: information_schema and not-null constraints - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: information_schema and not-null constraints
Date
Msg-id ea9fd77b-3feb-3f6b-1865-aa9d19b2c68a@eisentraut.org
Whole thread Raw
In response to Re: information_schema and not-null constraints  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: information_schema and not-null constraints
List pgsql-hackers
On 14.09.23 10:20, Peter Eisentraut wrote:
> On 06.09.23 19:52, Alvaro Herrera wrote:
>> +    SELECT current_database()::information_schema.sql_identifier AS 
>> constraint_catalog,
>> +           rs.nspname::information_schema.sql_identifier AS 
>> constraint_schema,
>> +           con.conname::information_schema.sql_identifier AS 
>> constraint_name,
>> +           format('CHECK (%s IS NOT NULL)', 
>> at.attname)::information_schema.character_data AS check_clause
> 
> Small correction here: This should be
> 
> pg_catalog.format('%s IS NOT NULL', 
> at.attname)::information_schema.character_data AS check_clause
> 
> That is, the word "CHECK" and the parentheses should not be part of the
> produced value.

I have committed this fix.



pgsql-hackers by date:

Previous
From: Suraj Kharage
Date:
Subject: Re: Server crash on RHEL 9/s390x platform against PG16
Next
From: Andy Fan
Date:
Subject: Re: make add_paths_to_append_rel aware of startup cost