postgresql/contrib/dblink
Joe Conway cd1e23e93b Fix ancient connection leak in dblink
When using unnamed connections with dblink, every time a new
connection is made, the old one is leaked. Fix that.

This has been an issue probably since dblink was first committed.
Someone complained almost ten years ago, but apparently I decided
not to pursue it at the time, and neither did anyone else, so it
slipped between the cracks. Now that someone else has complained,
fix in all supported branches.

Discussion: (orig) https://postgr.es/m/flat/F680AB59-6D6F-4026-9599-1BE28880273D%40decibel.org#F680AB59-6D6F-4026-9599-1BE28880273D@decibel.org
Discussion: (new) https://postgr.es/m/flat/0A3221C70F24FB45833433255569204D1F6ADF8C@G01JPEXMBYT05
Reported by: Jim Nasby and Takayuki Tsunakawa
2017-03-11 13:32:18 -08:00
..
expected chomp PQerrorMessage() in backend uses 2017-02-27 08:54:51 -05:00
input
output
sql Establish conventions about global object names used in regression tests. 2016-07-17 18:42:43 -04:00
.gitignore
dblink--1.0--1.1.sql
dblink--1.1--1.2.sql Fix parallel-safety markings for contrib/dblink. 2016-06-17 23:08:21 -04:00
dblink--1.2.sql Fix parallel-safety markings for contrib/dblink. 2016-06-17 23:08:21 -04:00
dblink--unpackaged--1.0.sql
dblink.c Fix ancient connection leak in dblink 2017-03-11 13:32:18 -08:00
dblink.control Update dblink extension for parallel query. 2016-06-17 15:18:44 -04:00
Makefile Update dblink extension for parallel query. 2016-06-17 15:18:44 -04:00
pg_service.conf