On Wed, Apr 15, 2026 at 7:51 AM PG Doc comments form <[email protected]> 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.
