Re: UPDATE column without FK fires other FK triggers constraint check

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Luca Looz <luca(dot)looz92(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: UPDATE column without FK fires other FK triggers constraint check
Date: 2017-07-19 22:14:36
Message-ID: 2782.1500502476@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Luca Looz <luca(dot)looz92(at)gmail(dot)com> writes:
> Thanks for the explanation!
> Can these checks be implemented or the data needed is not there and adding
> it will only add an overhead for the majority of use cases?

It's hard to see how to do much better than we're doing without storing
more data on-disk than is there now. Whether that would be a good
tradeoff is dubious.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Matthew Byrne 2017-07-19 22:21:58 Re: Support for \u0000?
Previous Message Evan Martin 2017-07-19 22:11:50 Re: Why would log_lock_waits affect a query plan?