Don't try to open visibilitymap when analyzing a foreign table

Heikki Linnakangas <heikki.linnakangas@iki.fi>

Commit: 049ef3398d05c9dc8f48aa9a6d68440661cfeb87
Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
Date: 2023-12-08T07:16:21Z
Releases: 17.0
Don't try to open visibilitymap when analyzing a foreign table

It's harmless, visibilitymap_count() returns 0 if the file doesn't
exist. But it's also very pointless. I noticed this when I added an
assertion in smgropen() that the relnumber is valid.

Discussion: https://www.postgresql.org/message-id/621a52fd-3cd8-4f5d-a561-d510b853bbaf@iki.fi

Files

PathChange+/−
src/backend/commands/analyze.c modified +4 −1
src/backend/storage/smgr/smgr.c modified +2 −0

Discussion