public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: BUG #19444: conkey field empty for domain NOT NULL constraint in pg_constraint (18.3)
Date: Mon, 30 Mar 2026 14:44:18 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

PG Bug reporting form <[email protected]> writes:
> 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.

I do not think this is a bug.  The system catalog documentation says

    conkey int2[] (references pg_attribute.attnum)

      If a table constraint (including foreign keys, but not
      constraint triggers), list of the constrained columns

So (a) this is not a table constraint, and (b) a domain does not have
columns.

			regards, tom lane

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: BUG #19444: conkey field empty for domain NOT NULL constraint in pg_constraint (18.3)
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox