Skip to content

Commit 643428c

Browse files
committed
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
1 parent e3ebcca commit 643428c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/backend/utils/cache/inval.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -622,9 +622,9 @@ LocalExecuteInvalidationMessage(SharedInvalidationMessage *msg)
622622
else if (msg->id == SHAREDINVALSNAPSHOT_ID)
623623
{
624624
/* We only care about our own database and shared catalogs */
625-
if (msg->rm.dbId == InvalidOid)
625+
if (msg->sn.dbId == InvalidOid)
626626
InvalidateCatalogSnapshot();
627-
else if (msg->rm.dbId == MyDatabaseId)
627+
else if (msg->sn.dbId == MyDatabaseId)
628628
InvalidateCatalogSnapshot();
629629
}
630630
else

0 commit comments

Comments
 (0)