aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/execProcnode.c
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2017-03-08 23:43:38 +0900
committerFujii Masao <fujii@postgresql.org>2017-03-08 23:43:38 +0900
commit77d21970ae19418f321e6a76ddf1a57ae999c77a (patch)
treebd69b60fa717c4a058e9bcd47663f2c3b883dc94 /src/backend/executor/execProcnode.c
parent044d9efb6c97d65247a1287e7676de0ee75b3cfe (diff)
downloadpostgresql-77d21970ae19418f321e6a76ddf1a57ae999c77a.tar.gz
postgresql-77d21970ae19418f321e6a76ddf1a57ae999c77a.zip
Fix connection leak in DROP SUBSCRIPTION command, take 2.
Commit 898a792eb8283e31efc0b6fcbc03bbcd5f7df667 fixed the connection leak issue, but it was an unreliable way of bugfix. This bugfix was assuming that walrcv_command() subroutine cannot throw an error, but it's untenable assumption. For example, if it will be changed so that an error is thrown, connection leak issue will happen again. This patch ensures that the connection is closed even when walrcv_command() subroutine throws an error. Patch by me, reviewed by Petr Jelinek and Michael Paquier Discussion: https://www.postgresql.org/message-id/2058.1487704345@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/execProcnode.c')
0 files changed, 0 insertions, 0 deletions