Re: [HACKERS] v6.5.2 vacuum...? - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [HACKERS] v6.5.2 vacuum...?
Date
Msg-id Pine.BSF.4.10.9909182029040.27097-100000@thelab.hub.org
Whole thread Raw
In response to Re: [HACKERS] v6.5.2 vacuum...?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] v6.5.2 vacuum...?  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] v6.5.2 vacuum...?  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Okay, was able to do a subsequent vacuum and vacuum analyze...but, the
psql was running onthe same machine as the server, so I'm curious as to
why it would have disconnected...?

Also, side note...\h vacuum shows that 'vacuum [verbose] analyze' should
work, but if you try and run it,it gives an error...error in psql's help,
or the backend?


On Sat, 18 Sep 1999, Tom Lane wrote:

> The Hermit Hacker <scrappy@hub.org> writes:
> > Just tried to do a vacuum analyze on a new database, and the backend
> > started spewing out:
> 
> > FATAL: pq_endmessage failed: errno=32
> > pq_flush: send() failed: Broken pipe
> > FATAL: pq_endmessage failed: errno=32
> > pq_flush: send() failed: Broken pipe
> > FATAL: pq_endmessage failed: errno=32
> > pq_flush: send() failed: Broken pipe
> > FATAL: pq_endmessage failed: errno=32
> 
> I'm not seeing it here with a REL6_5 build from Thursday.  It looks
> suspiciously like a problem I thought I'd fixed a good while back,
> wherein the backend didn't behave too gracefully if the client
> disconnected early.
> 
>             regards, tom lane
> 

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



pgsql-hackers by date:

Previous
From: Michael Alan Dorman
Date:
Subject: Re: [HACKERS] Re: HISTORY for 6.5.2
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] case bug?