Use table/index_close() more consistently master github/master
authorMichael Paquier <[email protected]>
Thu, 18 Dec 2025 22:55:58 +0000 (07:55 +0900)
committerMichael Paquier <[email protected]>
Thu, 18 Dec 2025 22:55:58 +0000 (07:55 +0900)
commit9d0f7996e58c2a92efe06c901c6dfe1f6ced0a1d
tree546a3587185dd76ac90be9c30b8cbbd4e341cf41
parentd49936f3028b0bb6ac8ff83e07e421ca2a4f5c3f
Use table/index_close() more consistently

All the code paths updated here have been using relation_close() to
close a relation that has already been opened with table_open() or
index_open(), where a relkind check is enforced.

table_close() and index_open() do the same thing as relation_close(), so
there was no harm, but being inconsistent could lead to issues if the
internals of these close() functions begin to introduce some logic
specific to each relkind in the future.

Author: Bertrand Drouvot <[email protected]>
Discussion: https://postgr.es/m/[email protected]
src/backend/access/brin/brin.c
src/backend/parser/parse_utilcmd.c