15.14.1.023

fix: incorporate v3.0.0 supautils (#1844)

* fix: incorporate v3.0.0 supautils
with change that checks that an event trigger function is owned by the same superuser
negating the need for after-create for postgresql_fdw
introduces a test in pg_regress that checks the outcome of this change

* fix: add `grant usage` for postgres_fdw

* test: postgres_fdw

* fix: align expected output with test

* chore: update versions

---------

Co-authored-by: Bobbie Soedirgo <[email protected]>

15.14.1.021-plpgsql-4

fix: maintains security hardening while allowing the infrastructure t…

17.6.1.023-supautils-2

fix: add `grant usage` for postgres_fdw

17.6.1.023-supautils-1

fix: incorporate v3.0.0 supautils

with change that checks that an event trigger function is owned by the same superuser
negating the need for after-create for postgresql_fdw
introduces a test in pg_regress that checks the outcome of this change

17.5.1.044-orioledb-supautils-2

fix: add `grant usage` for postgres_fdw

17.5.1.044-orioledb-supautils-1

fix: incorporate v3.0.0 supautils

with change that checks that an event trigger function is owned by the same superuser
negating the need for after-create for postgresql_fdw
introduces a test in pg_regress that checks the outcome of this change

15.14.1.023-supautils-2

fix: add `grant usage` for postgres_fdw

15.14.1.023-supautils-1

fix: incorporate v3.0.0 supautils

with change that checks that an event trigger function is owned by the same superuser
negating the need for after-create for postgresql_fdw
introduces a test in pg_regress that checks the outcome of this change

17.6.1.022

chore: systemd hardening (#1837)

* chore: systemd hardening

ProtectHome and InaccessiblePaths to senstive internal locations

* Apply suggestion from @pcnc

Co-authored-by: Paul Cioanca <[email protected]>

* chore: more paths

---------

Co-authored-by: Paul Cioanca <[email protected]>

17.6.1.021-plpgsql-3

chore: bump suffix to rebuild