Well, ok it's a known problem. Patched but apparently pending the
release cycle.
> Admins,
>
> Drop database even with (force) hangs indefinately unless the pgl
> supervisor is term'd.
----
REL2_x_STABLE:pglogical$ git log -n1
commit f27d3c4 (HEAD -> REL2_x_STABLE, origin/REL2_x_STABLE, origin/HEAD)
Author: Euler Taveira <euler.taveira@enterprisedb.com>
Date: Mon Nov 28 10:38:26 2022 -0300
Drop database never completes in Postgres 15 (#403)
Postgres 15 introduced a signal barrier for DROP DATABASE
(4eb2176318d0561846c1f9fb3c68bede799d640f). pglogical has no logic to
handle it in the supervisor code. Add CFI to fix it.
Fix #399
REL2_x_STABLE:pglogical$ git log -n1 REL2_4_2
commit 740f1f3 (tag: REL2_4_2)
Author: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Date: Wed Oct 12 13:55:10 2022 +0200
pglogical 2.4.2 release notes and docs update (#357)
Update release notes for 2.4.2
Add PG 15 package descriptions
REL2_x_STABLE:pglogical$
Jerry Sievers <gsievers19@comcast.net> writes:
>
> PostgreSQL 15.1 (Ubuntu 15.1-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1)
9.4.0,64-bit
>
> This particular cluster I don't believe needs pgl but we have it
> nonetheless config'd in shared_preload_libs as to enable it if necessary
> without a restart.
>
> I"ve not checked yet the rel notes for pg15.2 in case of any change in
> this regard.
>
> Will raise this with the pglogical community also perhaps."
>
>
> dpkg says this about our pglogical version.
>
> ii postgresql-15-pglogical 2.4.2-2.pgdg20.04+1 amd64 Logical Replication
Extensionfor PostgreSQL
>
>
> Any advice?
>
> Thx!
