Movatterモバイル変換


[0]ホーム

URL:


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

Sign up
Appearance settings

Commit30803bd

Browse files
committed
Fix inconsistent code with shared invalidations of snapshots
The code in charge of processing a single invalidation message has beenusing since568d413 the structure for relation mapping messages. Thishad fortunately no consequence as both locate the database ID at thesame location, but it could become a problem in the future if this areaof the code changes.Author: Konstantin KnizhnikDiscussion:https://postgr.es/m/8044c223-4d3a-2cdb-42bf-29940840ce94@postgrespro.ruBackpatch-through: 9.5
1 parent546f143 commit30803bd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -619,9 +619,9 @@ LocalExecuteInvalidationMessage(SharedInvalidationMessage *msg)
619619
elseif (msg->id==SHAREDINVALSNAPSHOT_ID)
620620
{
621621
/* We only care about our own database and shared catalogs */
622-
if (msg->rm.dbId==InvalidOid)
622+
if (msg->sn.dbId==InvalidOid)
623623
InvalidateCatalogSnapshot();
624-
elseif (msg->rm.dbId==MyDatabaseId)
624+
elseif (msg->sn.dbId==MyDatabaseId)
625625
InvalidateCatalogSnapshot();
626626
}
627627
else

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp