summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2020-12-28 22:17:16 +0900
committerMichael Paquier <michael@paquier.xyz>2020-12-28 22:17:16 +0900
commit7bf20c1b8a14022c59631a2b1ce6d1e41e9494ad (patch)
treeaeb4b6f45d99583de46a73b50eed422b7e2ed9ca /src
parent03b7a1ee7b7ff037156c2357eaf545e515ad6455 (diff)
Fix inconsistent code with shared invalidations of snapshots
The code in charge of processing a single invalidation message has been using since 568d413 the structure for relation mapping messages. This had fortunately no consequence as both locate the database ID at the same location, but it could become a problem in the future if this area of the code changes. Author: Konstantin Knizhnik Discussion: https://postgr.es/m/8044c223-4d3a-2cdb-42bf-29940840ce94@postgrespro.ru Backpatch-through: 9.5
Diffstat (limited to 'src')
-rw-r--r--src/backend/utils/cache/inval.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/utils/cache/inval.c b/src/backend/utils/cache/inval.c
index 8e9125a12df..2a05f602613 100644
--- a/src/backend/utils/cache/inval.c
+++ b/src/backend/utils/cache/inval.c
@@ -609,9 +609,9 @@ LocalExecuteInvalidationMessage(SharedInvalidationMessage *msg)
else if (msg->id == SHAREDINVALSNAPSHOT_ID)
{
/* We only care about our own database and shared catalogs */
- if (msg->rm.dbId == InvalidOid)
+ if (msg->sn.dbId == InvalidOid)
InvalidateCatalogSnapshot();
- else if (msg->rm.dbId == MyDatabaseId)
+ else if (msg->sn.dbId == MyDatabaseId)
InvalidateCatalogSnapshot();
}
else