Unix Technical Forum

Re: BUG #3808: Connections stays open in stateCLOSE_WAIT

This is a discussion on Re: BUG #3808: Connections stays open in stateCLOSE_WAIT within the pgsql Bugs forums, part of the PostgreSQL category; --> "Dave Page" <dpage@postgresql.org> writes: >> From: Bruce Momjian <bruce@momjian.us> >> Should we require the form to tell us their ...


Go Back   Unix Technical Forum > Database Server Software > PostgreSQL > pgsql Bugs

Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-10-2008, 11:12 AM
Tom Lane
 
Posts: n/a
Default Re: BUG #3808: Connections stays open in stateCLOSE_WAIT

"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 the 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

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 04-10-2008, 11:13 AM
Daniel Migowski
 
Posts: n/a
Default Re: BUG #3808: Connections stays open in stateCLOSE_WAIT

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 ensure the 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




Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 12:53 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com