From: Andrew Dunstan <andrew@dunslane.net>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix new Object Access hooks test
Date: Tue, 22 Mar 2022 17:35:40 +0000
Message-ID: <E1nWiPz-000tiy-Vk@gemulon.postgresql.org> (raw)
Fix new Object Access hooks test
Commit 90efa2f556 caused some issues with EXEC_BACKEND builds and with
force_parallel_mode = regress setups. For the first issue we no longer
test if the module has been preloaded, and in fact we don't preload it,
but simply LOAD it in the test script. For the second issue we suppress
error messages emanating from parallel workers.
Mark Dilger
Discussion: https://postgr.es/m/7f6d54a1-4024-3b6e-e3ec-26cd394aac9e@dunslane.net
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/f0206d99520ebdb751469ad53ff62bbff817ab3d
Modified Files
--------------
src/test/modules/test_oat_hooks/Makefile | 3 ---
src/test/modules/test_oat_hooks/expected/test_oat_hooks.out | 1 +
src/test/modules/test_oat_hooks/sql/test_oat_hooks.sql | 1 +
src/test/modules/test_oat_hooks/test_oat_hooks.c | 12 ++----------
src/test/modules/test_oat_hooks/test_oat_hooks.conf | 1 -
5 files changed, 4 insertions(+), 14 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: andrew@dunslane.net
Subject: Re: pgsql: Fix new Object Access hooks test
In-Reply-To: <E1nWiPz-000tiy-Vk@gemulon.postgresql.org>
References: <E1nWiPz-000tiy-Vk@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox