Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Marcus Gartner <marcus(at)cockroachlabs(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types
Date: 2021-11-01 23:14:32
Message-ID: 202111012314.qcqulwshoxfx@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2021-Nov-01, Marcus Gartner wrote:

> I agree with you there. So why is an FK relationship between columns of
> different types even allowed?

It is useful in other cases, such as varchar or int4/int8.

Please don't top-post.

--
Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
Are you not unsure you want to delete Firefox?
[Not unsure] [Not not unsure] [Cancel]
http://smylers.hates-software.com/2008/01/03/566e45b2.html

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2021-11-02 00:13:47 Re: BUG #17245: Index corruption involving deduplicated entries
Previous Message Alvaro Herrera 2021-11-01 23:12:39 Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types