aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2020-12-28 22:17:06 +0900
committerMichael Paquier <michael@paquier.xyz>2020-12-28 22:17:06 +0900
commit6819380dd2655f1790d760b13a81f3d27dbe685a (patch)
tree50d7c8a8680dd145b58f1a6f2af84e6599f13b18
parent294cdd7d0fffbaadf0f35202a30aab2863e6106a (diff)
downloadpostgresql-6819380dd2655f1790d760b13a81f3d27dbe685a.tar.gz
postgresql-6819380dd2655f1790d760b13a81f3d27dbe685a.zip
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
-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 80bc7740fe8..c7dc8267cf7 100644
--- a/src/backend/utils/cache/inval.c
+++ b/src/backend/utils/cache/inval.c
@@ -619,9 +619,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