]> git.ipfire.org Git - thirdparty/postgresql.git/commit
projects / thirdparty / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: cd7f19d) | patch
Don't try to open visibilitymap when analyzing a foreign table
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>
Fri, 8 Dec 2023 07:16:21 +0000 (09:16 +0200)
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>
Fri, 8 Dec 2023 07:16:21 +0000 (09:16 +0200)
commit049ef3398d05c9dc8f48aa9a6d68440661cfeb87
tree718bb792e696864fc04cf9717daea0f0e798e722tree | snapshot
parentcd7f19da34684b7b12fdc08511c5ce7bebb09419commit | diff
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
src/backend/commands/analyze.c diff | blob | blame | history
src/backend/storage/smgr/smgr.c diff | blob | blame | history
Mirror of https://git.postgresql.org/git/postgresql.git