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

diff --git a/src/backend/utils/cache/inval.c b/src/backend/utils/cache/inval.c
index 80bc7740fe8c6e0090ce431a8e92ac0e74e53bf2..c7dc8267cf7210448ab39c3ace81c55f7651825e 100644 (file)
--- 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