From: Tom Lane <tgl@sss.pgh.pa.us>
To: marcus@cockroachlabs.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types
Date: Mon, 01 Nov 2021 17:59:49 -0400
Message-ID: <1311165.1635803989@sss.pgh.pa.us> (raw)
In-Reply-To: <17261-b27dbaa13eba2220@postgresql.org>
References: <17261-b27dbaa13eba2220@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> It is possible to break foreign key referential integrity when the FK
> columns have different types and updates are cascaded from the parent
> relation to the child relation.
I'm not really sure what you'd consider such an FK relationship to mean.
I can't get too excited about it when there doesn't seem to be a well
defined semantics for it.
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, marcus@cockroachlabs.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types
In-Reply-To: <1311165.1635803989@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox