| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Subject: | Re: information_schema and not-null constraints |
| Date: | 2023-09-18 06:15:53 |
| Message-ID: | ea9fd77b-3feb-3f6b-1865-aa9d19b2c68a@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2023-09-18 06:38:09 | Re: make add_paths_to_append_rel aware of startup cost |
| Previous Message | Suraj Kharage | 2023-09-18 05:50:41 | Re: Server crash on RHEL 9/s390x platform against PG16 |