Re: should ConstraintRelationId ins/upd cause relcache invals?
| От | Alvaro Herrera |
|---|---|
| Тема | Re: should ConstraintRelationId ins/upd cause relcache invals? |
| Дата | |
| Msg-id | 201901212240.rrxptrl6vyek@alvherre.pgsql обсуждение исходный текст |
| Ответ на | Re: should ConstraintRelationId ins/upd cause relcache invals? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: should ConstraintRelationId ins/upd cause relcache invals?
|
| Список | 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 по дате отправления: