mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-03 02:37:22 +02:00
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
This commit is contained in:
parent
294cdd7d0f
commit
6819380dd2
4
src/backend/utils/cache/inval.c
vendored
4
src/backend/utils/cache/inval.c
vendored
@ -619,9 +619,9 @@ LocalExecuteInvalidationMessage(SharedInvalidationMessage *msg)
|
|||||||
else if (msg->id == SHAREDINVALSNAPSHOT_ID)
|
else if (msg->id == SHAREDINVALSNAPSHOT_ID)
|
||||||
{
|
{
|
||||||
/* We only care about our own database and shared catalogs */
|
/* We only care about our own database and shared catalogs */
|
||||||
if (msg->rm.dbId == InvalidOid)
|
if (msg->sn.dbId == InvalidOid)
|
||||||
InvalidateCatalogSnapshot();
|
InvalidateCatalogSnapshot();
|
||||||
else if (msg->rm.dbId == MyDatabaseId)
|
else if (msg->sn.dbId == MyDatabaseId)
|
||||||
InvalidateCatalogSnapshot();
|
InvalidateCatalogSnapshot();
|
||||||
}
|
}
|
||||||
else
|
else
|
||||||
|
Loading…
Reference in New Issue
Block a user