Re: Example. Foreign Keys Constraints. Wrong Columns

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: postgresql(dot)org(dot)reach457(at)passmail(dot)net, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Example. Foreign Keys Constraints. Wrong Columns
Date: 2026-04-15 15:23:34
Message-ID: CAKFQuwbm4BD49A8ZqjZnxHKW8MsEURa6hrEvAWKxw0_nu=FZwg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Wed, Apr 15, 2026 at 7:51 AM PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:

> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/18/ddl-constraints.html
> Description:
>
>
> https://www.postgresql.org/docs/current/ddl-constraints.html#DDL-CONSTRAINTS-FK
>
>
Given that users has:

> PRIMARY KEY (tenant_id, user_id)
>
>
This:

> FOREIGN KEY (tenant_id, author_id) REFERENCES users ON DELETE SET NULL
> (author_id)
>
>
And this:

> FOREIGN KEY (tenant_id, author_id) REFERENCES users (tenant_id,
> user_id)
> ON DELETE SET NULL (author_id)
>

Produce an identical outcome.

The absence of a column list on the former causes the system to look at the
primary key for the named table and use its column list - which is
(tenant_id, user_id), same as the later explicit version.

David J.

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message David G. Johnston 2026-04-15 15:55:20 Re: Logical Replication upgrade
Previous Message Yushu Chen 2026-04-15 09:45:41 Re: doc: Clarify ANALYZE VERBOSE output