Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 7bf20c1

Browse filesBrowse 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 03b7a1e commit 7bf20c1
Copy full SHA for 7bf20c1

File tree

Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed

‎src/backend/utils/cache/inval.c

Copy file name to clipboardExpand all lines: src/backend/utils/cache/inval.c
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -609,9 +609,9 @@ LocalExecuteInvalidationMessage(SharedInvalidationMessage *msg)
609609
else if (msg->id == SHAREDINVALSNAPSHOT_ID)
610610
{
611611
/* We only care about our own database and shared catalogs */
612-
if (msg->rm.dbId == InvalidOid)
612+
if (msg->sn.dbId == InvalidOid)
613613
InvalidateCatalogSnapshot();
614-
else if (msg->rm.dbId == MyDatabaseId)
614+
else if (msg->sn.dbId == MyDatabaseId)
615615
InvalidateCatalogSnapshot();
616616
}
617617
else

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.