postgres.git / summary / log / commit / refs

commit    1c7ca6178963c4bb2f53dbdcc6c444db758c84a5
Author:   Michael Paquier <michael@paquier.xyz>
Date:     Mon Dec 28 13:17:11 2020 +0000
First released in: 14.0, 9.5.25, 9.6.21, 10.16, 11.11, 12.6, 13.2

    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


 src/backend/utils/cache/inval.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/backend/utils/cache/inval.c b/src/backend/utils/cache/inval.c
index cfaad4b22fb..e507f320217 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


[parent: 744357d8461c]