mirror of
https://github.com/postgres/postgres.git
synced 2025-11-25 12:03:53 +03:00
At end of recovery, reset all sinval-managed caches.
An inplace update's invalidation messages are part of its transaction's commit record. However, the update survives even if its transaction aborts or we stop recovery before replaying its transaction commit. After recovery, a backend that started in recovery could update the row without incorporating the inplace update. That could result in a table with an index, yet relhasindex=f. That is a source of index corruption. This bulk invalidation avoids the functional consequences. A future change can fix the !RecoveryInProgress() scenario without changing the WAL format. Back-patch to v17 - v12 (all supported versions). v18 will instead add invalidations to WAL. Discussion: https://postgr.es/m/20240618152349.7f.nmisch@google.com
This commit is contained in:
@@ -35,6 +35,7 @@ extern void SharedInvalBackendInit(bool sendOnly);
|
||||
extern void SIInsertDataEntries(const SharedInvalidationMessage *data, int n);
|
||||
extern int SIGetDataEntries(SharedInvalidationMessage *data, int datasize);
|
||||
extern void SICleanupQueue(bool callerHasWriteLock, int minFree);
|
||||
extern void SIResetAll(void);
|
||||
|
||||
extern LocalTransactionId GetNextLocalTransactionId(void);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user