Thread: Re: BUG #3808: Connections stays open in stateCLOSE_WAIT

> ------- Original Message -------
> From: Bruce Momjian <bruce@momjian.us>
> To: Dave Page <dpage@postgresql.org>
> Sent: 16/12/07, 10:08:17
> Subject: Re: [BUGS] BUG #3808: Connections stays open in stateCLOSE_WAIT
>
> > Make sure you are running the latest available minor release for your
> > major version before reporting a bug. The current list of supported
> > versions is 8.2.5, 8.1.10, 8.0.14, 7.4.18.
>
> Should we require the form to tell us their exact version number and
> throw an error if it isn't the current one?

Past experience with other bug systems tells me we'll just end up with people selecting the lastest version to ensure
theform is accepted, thus making it even harder for us to figure out what the problem really is. 

/D

"Dave Page" <dpage@postgresql.org> writes:
>> From: Bruce Momjian <bruce@momjian.us>
>> Should we require the form to tell us their exact version number and
>> throw an error if it isn't the current one?

> Past experience with other bug systems tells me we'll just end up with people selecting the lastest version to ensure
theform is accepted, thus making it even harder for us to figure out what the problem really is. 

Agreed, that's a pretty awful idea.  It's hard enough to get accurate
version information, even without creating an incentive for people to
lie.  Moreover, of those that are too honest to do that, a lot would
simply never file a report; thus keeping us from hearing about a problem
that might well still exist.

            regards, tom lane

Tom Lane schrieb:
> "Dave Page" <dpage@postgresql.org> writes:
>
>>> From: Bruce Momjian <bruce@momjian.us>
>>> Should we require the form to tell us their exact version number and
>>> throw an error if it isn't the current one?
>>>
>
>
>> Past experience with other bug systems tells me we'll just end up with people selecting the lastest version to
ensurethe form is accepted, thus making it even harder for us to figure out what the problem really is. 
>>
>
> Agreed, that's a pretty awful idea.  It's hard enough to get accurate
> version information, even without creating an incentive for people to
> lie.  Moreover, of those that are too honest to do that, a lot would
> simply never file a report; thus keeping us from hearing about a problem
> that might well still exist.
>
>             regards, tom lane
>
The problem seems to be fixed in the current version. Btw. if there
hasn't been a similar bug report before, it is still okey to post it,
for all others who will have the same problem again and can read in the
mailing list if a solution is the upgrade. You now, never touch a
running system, especially if it's running a highly used production site.

Btw. the update went without a glitch and was done in 5 Minutes, good
work for that. But I didn't know that and asking before having to
restore something for hours because of a failed update seems legitimate
to me.

With best regards,
Daniel Migowski