Re: Fix optimization of foreign-key on update actions
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andrew Gierth <andrew@tao11.riddles.org.uk>
Date: 2019-03-18T17:02:52Z
Lists: pgsql-hackers
On 2019-03-11 12:57, Peter Eisentraut wrote: > On 2019-02-06 23:15, Peter Eisentraut wrote: >> On 05/02/2019 17:20, Tom Lane wrote: >>> What I *don't* like about the proposed patch is that it installs a >>> new, different comparison rule for the ON UPDATE CASCADE case only. >>> If we were to go in this direction, I'd think we should try to use >>> the same comparison rule for all FK row comparisons. >> >> That's easy to change. I had it like that in earlier versions of the >> patch. I agree it would be better for consistency, but it would create >> some cases where we do unnecessary extra work. > > Updated patch with this change made, and some conflicts resolved. Committed like this. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix optimization of foreign-key on update actions
- 1ffa59a85cb4 12.0 landed