Re: Subscription test 013_partition.pl fails under CLOBBER_CACHE_ALWAYS
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-09-16T03:49:36Z
Lists: pgsql-hackers
On Wed, Sep 16, 2020 at 1:16 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > I wrote: > It's not really clear to me why setting localreloid to zero is a sane > way to represent "this entry needs to be revalidated". I think a > separate flag would be more appropriate. Once we have lock on the > target relation, it seems to me that no interesting changes should > be possible as long as we have lock; so there's no very good reason > to destroy useful state to remind ourselves that we should recheck > it next time. > So, can we assume that the current code can only cause the problem in CCA builds bot not in any practical scenario because after having a lock on relation probably there shouldn't be any invalidation which leads to this problem? -- With Regards, Amit Kapila.
Commits
-
Fix bogus cache-invalidation logic in logical replication worker.
- d6d70f89a6f9 10.15 landed
- 8580631ff77c 12.5 landed
- 3e3f8f20206c 13.0 landed
- 3d65b0593c55 14.0 landed
- 2c74f7139edd 11.10 landed