Re: [HACKERS] [bug fix] dblink leaks unnamed connections - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] [bug fix] dblink leaks unnamed connections
Date
Msg-id 20926.1489074851@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] [bug fix] dblink leaks unnamed connections  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: [HACKERS] [bug fix] dblink leaks unnamed connections  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
Fujii Masao <masao.fujii@gmail.com> writes:
> On Wed, Mar 8, 2017 at 3:52 PM, Tsunakawa, Takayuki
> <tsunakawa.takay@jp.fujitsu.com> wrote:
>> dblink fails to close the unnamed connection as follows when a new unnamed connection is requested.  The attached
patchfixes this. 

> This issue was reported about ten years ago and added as TODO item.
> http://archives.postgresql.org/pgsql-hackers/2007-10/msg00895.php

> I agree that this is a bug, and am tempted to back-patch to all the supported
> versions. But it had not been fixed in many years since the first report of
> the issue. So I'm not sure if it's ok to just treat this as a bug right now and
> back-patch. Or we should fix this only in HEAD? Anyway I'd like to hear
> more opinions about this.

It looks to me like the issue simply fell through the cracks because Joe
wasn't excited about fixing it.  Now that we have a second complaint,
I think it's worth treating as a bug and back-patching.

(I've not read this particular patch and am not expressing an opinion
whether it's correct.)
        regards, tom lane



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: [HACKERS] Parallel Bitmap scans a bit broken
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] use SQL standard error code for nextval