Hi, On 2019-01-21 19:40:17 -0300, Alvaro Herrera wrote: > On 2019-Jan-21, Tom Lane wrote: > > > Alvaro Herrera <alvhe...@2ndquadrant.com> writes: > > > > At https://postgr.es/m/201901182216.nr5clsxrn624@alvherre.pgsql I posted > > > a simplistic for the specific problem I found by calling > > > CacheInvalidateRelcache in the problem spot. But I'm wondering if the > > > correct fix isn't to have CacheInvalidateHeapTuple deal with FK > > > pg_constraint tuples instead, per the attached patch. > > > > +1, this is safer than expecting retail relcache inval calls to be > > added in all the right places. > > Thanks, pushed.
Given https://www.postgresql.org/message-id/20190121193300.gknn7p4pmmjg7nqf%40alap3.anarazel.de and the concerns voiced in the thread quoted therein, I'm a bit surprised that you just went ahead with this, and backpatched it to boot. Greetings, Andres Freund
