1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix inconsistent code with shared invalidations of snapshots

Browse Source 
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
This commit is contained in:
Michael Paquier 2020-12-28 22:17:16 +09:00
parent 03b7a1ee7b
commit 7bf20c1b8a
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/backend/utils/cache/inval.c vendored
View File

@ -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