Re: should ConstraintRelationId ins/upd cause relcache invals? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: should ConstraintRelationId ins/upd cause relcache invals?
Date
Msg-id 201901212240.rrxptrl6vyek@alvherre.pgsql
Whole thread Raw
In response to Re: should ConstraintRelationId ins/upd cause relcache invals?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: should ConstraintRelationId ins/upd cause relcache invals?
List pgsql-hackers
On 2019-Jan-21, Tom Lane wrote:

> Alvaro Herrera <alvherre@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.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: COPY FROM WHEN condition
Next
From: Andres Freund
Date:
Subject: Re: should ConstraintRelationId ins/upd cause relcache invals?