Re: [HACKERS] v6.5.2 vacuum...?

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] v6.5.2 vacuum...?
Date: 1999-09-18 23:30:23
Message-ID: Pine.BSF.4.10.9909182029040.27097-100000@thelab.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)hub(dot)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(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-09-18 23:31:27 Re: [HACKERS] case bug?
Previous Message Michael Alan Dorman 1999-09-18 22:38:55 Re: [HACKERS] Re: HISTORY for 6.5.2