Re: Subscription test 013_partition.pl fails under CLOBBER_CACHE_ALWAYS
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@lists.postgresql.org
Date: 2020-09-15T21:30:15Z
Lists: pgsql-hackers
Attachments
- fix-logical-rep-cache-flush.patch (text/x-diff) patch
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. Here's a patch that changes that, and also cleans up some sloppy thinking about how to re-acquire lock on the replication target relation. (Just because the OID was valid last you heard does not mean that table_open is guaranteed to succeed.) With this, we get through 013_partition.pl under CCA. I plan to try to run all of subscription/ and recovery/ before concluding there's nothing else to fix, though. regards, tom lane
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