Fujii Masao <fu...@postgresql.org> writes:
> Fix connection leak in DROP SUBSCRIPTION command.
> Previously the command forgot to close the connection to the publisher
> when it failed to drop the replication slot.
If there's a bug here, this seems like an extremely unreliable way of
fixing it. What if an error gets thrown before you reach that ereport?
In other words, this coding is assuming that the walrcv_command()
subroutine cannot throw an error, which I would consider dangerous
even if it were a fixed subroutine. If it's a hook that's doing
unknown stuff, that seems a completely untenable assumption. You
really need either to hook the cleanup action into normal error
recovery, or to use a PG_TRY block.
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
