Re: BUG #19444: conkey field empty for domain NOT NULL constraint in pg_constraint (18.3)

From: Junwang Zhao <zhjwpku(at)gmail(dot)com>
To: zheng_xianghang(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19444: conkey field empty for domain NOT NULL constraint in pg_constraint (18.3)
Date: 2026-03-30 14:17:19
Message-ID: CAEG8a3LtSo304Py+pRtd8KWU=-T8+8Aa2room8rJ2Oq6=Go5rA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Mar 30, 2026 at 7:52 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 19444
> Logged by: Xianghang Zheng
> Email address: zheng_xianghang(at)163(dot)com
> PostgreSQL version: 18.3
> Operating system: Linux x86_64
> Description:
>
> When creating a domain with a NOT NULL constraint, the conkey field in
> pg_constraint remains empty. This is inconsistent with table-level NOT
> NULL constraints, which correctly populate the conkey field.
>
> Version: PostgreSQL 18.3 (x86_64)
> Platform: Linux x86_64
>
> Steps to Reproduce:
> -------------------
> CREATE DOMAIN my_domain AS text NOT NULL;
>
> SELECT conname, contype, conkey, contypid::regtype
> FROM pg_constraint
> WHERE contypid = 'my_domain'::regtype;
>
> Actual Result:
> --------------
> conname | contype | conkey | contypid
> --------------------+---------+--------+-----------
> my_domain_not_null | n | | my_domain
> (1 row)
>
> Expected Result:
> ----------------
> The conkey field should contain {1} (the first and only column of the
> domain):
>
> conname | contype | conkey | contypid
> --------------------+---------+--------+-----------
> my_domain_not_null | n | {1} | my_domain
>
> Additional Information:
> -----------------------
> - The NOT NULL constraint works correctly (rejects NULL values)
> - The issue is only with the system catalog metadata
> - This may affect tools like pg_dump, pg_upgrade, or extensions that rely
> on the conkey field for domain constraints
> - Table-level NOT NULL constraints correctly populate conkey:
>
> CREATE TABLE test_table (id text NOT NULL);
> SELECT conname, contype, conkey FROM pg_constraint
> WHERE conrelid = 'test_table'::regclass;
>
> Result: test_table_id_not_null | n | {1}
>
> Please let me know if you need any additional information or testing.
>
>

I think you have interpreted this incorrectly, domain is a type, not a relation.
See the comments in pg_constraint.h for clarification.

/*
* conrelid and conkey are only meaningful if the constraint applies to a
* specific relation (this excludes domain constraints and assertions).
* Otherwise conrelid is 0 and conkey is NULL.
*/

>
>

--
Regards
Junwang Zhao

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Junwang Zhao 2026-03-30 14:39:23 Re: BUG #19442: PL/pgSQL: domain over composite type bypasses type validation when assigning NULL (PostgreSQL 18.3)
Previous Message Xuneng Zhou 2026-03-30 03:14:19 Re: BUG #19439: pg_stat_xact_user_tables stat not currect during the transaction