NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit441ef5e

committed

Fix relcache invalidation when relfilelocator is updated

In commitaf0e7de, I removed a call to RelationCloseSmgr(), becausethe dangling SMgrRelation was no longer an issue. However, we stillneed the call when the relation's relfilelocator changes, so that thenew relfilelocator takes effect immediately.Reported-by: Alexander Lakhin <exclusion@gmail.com>Discussion:https://www.postgresql.org/message-id/987b1c8c-8c91-4847-ca0e-879f421680ff%40gmail.com

1 parent90fe7b7 commit441ef5eCopy full SHA for 441ef5e

File tree

1 file changed

-0

lines changed

src/backend/utils/cache
- relcache.c

1 file changed

-0

lines changed

`‎src/backend/utils/cache/relcache.c`

Lines changed: 3 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -3060,7 +3060,10 @@ RelationCacheInvalidate(bool debug_discard)`
`3060`	`3060`	`* map doesn't involve any access to relcache entries.`
`3061`	`3061`	`*/`
`3062`	`3062`	`if (RelationIsMapped(relation))`
	`3063`	`+{`
	`3064`	`+RelationCloseSmgr(relation);`
`3063`	`3065`	`RelationInitPhysicalAddr(relation);`
	`3066`	`+}`
`3064`	`3067`
`3065`	`3068`	`/*`
`3066`	`3069`	`* Add this entry to list of stuff to rebuild in second pass.`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit441ef5e

File tree

1 file changed

1 file changed

`‎src/backend/utils/cache/relcache.c`

0 commit comments