Re: New Object Access Type hooks

On 3/22/22 12:02, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> That seems quite weird. I'm not sure how it's getting loaded at all if
>> not via shared_preload_libraries
> Some other animals are showing this:
>
> diff -U3 /home/postgres/pgsql/src/test/modules/test_oat_hooks/expected/test_oat_hooks.out /home/postgres/pgsql/src/test/modules/test_oat_hooks/results/test_oat_hooks.out
> --- /home/postgres/pgsql/src/test/modules/test_oat_hooks/expected/test_oat_hooks.out 2022-03-22 11:57:40.224991011 -0400
> +++ /home/postgres/pgsql/src/test/modules/test_oat_hooks/results/test_oat_hooks.out 2022-03-22 11:59:59.998983366 -0400
> @@ -48,6 +48,8 @@
> SELECT * FROM regress_test_table;
> NOTICE: in executor check perms: superuser attempting execute
> NOTICE: in executor check perms: superuser finished execute
> +NOTICE: in executor check perms: superuser attempting execute
> +NOTICE: in executor check perms: superuser finished execute
> t
> ---
> (0 rows)
> @@ -95,6 +97,8 @@
> ^
> NOTICE: in executor check perms: non-superuser attempting execute
> NOTICE: in executor check perms: non-superuser finished execute
> +NOTICE: in executor check perms: non-superuser attempting execute
> +NOTICE: in executor check perms: non-superuser finished execute
> t
> ---
> (0 rows)
> @@ -168,6 +172,8 @@
> ^
> NOTICE: in executor check perms: superuser attempting execute
> NOTICE: in executor check perms: superuser finished execute
> +NOTICE: in executor check perms: superuser attempting execute
> +NOTICE: in executor check perms: superuser finished execute
> t
> ---
> (0 rows)
>
>
> I can duplicate that by adding "force_parallel_mode = regress"
> to test_oat_hooks.conf, so a fair bet is that the duplication
> comes from executing the same hook in both leader and worker.
>
>

OK, thanks. My test didn't include that one setting :-(

If I can't com up with a very quick fix I'll revert it.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com