Fix some near-bugs related to ResourceOwner function arguments These functions took a ResourceOwner argument, but only checked if it was NULL, and then used CurrentResourceOwner for the actual work. Surely the intention was to use the passed-in resource owner. All current callers passed CurrentResourceOwner or NULL, so this has no consequences at the moment, but it's an accident waiting to happen for future caller and extensions.
Author: Matthias van de Meent <[email protected]> Discussion: https://www.postgresql.org/message-id/caeze2whnfv8vurzaohe-af+gxba1snfd_rxfm84jv-958uc...@mail.gmail.com Backpatch-through: 17 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/fa44b8b7fbb7eb0f13546aa13976f9919a4ca201 Modified Files -------------- src/backend/storage/aio/aio.c | 12 ++++++------ src/backend/utils/cache/catcache.c | 4 ++-- 2 files changed, 8 insertions(+), 8 deletions(-)
