Обсуждение: v6.5.2 vacuum...?

Поиск
Список
Период
Сортировка

v6.5.2 vacuum...?

От
The Hermit Hacker
Дата:
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

Fresh build of the server, FreeBSD 3.3...



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

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

От
Tom Lane
Дата:
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

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

От
The Hermit Hacker
Дата:
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

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

От
Tom Lane
Дата:
The Hermit Hacker <scrappy@hub.org> writes:
> 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?

???  Works for me ... in fact that's how I usually run vacuum:

play=> vacuum verbose analyze;
NOTICE:  --Relation pg_type--
NOTICE:  Pages 2: Changed 0, Reapped 1, Empty 0, New 0; Tup 114: Vac 1, Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 109,
MaxLen109; Re-using: Free/Avail. Space 3076/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
 
NOTICE:  Index pg_type_typname_index: Pages 2; Tuples 114: Deleted 1. Elapsed 0/0 sec.
NOTICE:  Index pg_type_oid_index: Pages 2; Tuples 114: Deleted 1. Elapsed 0/0 sec.
NOTICE:  --Relation pg_attribute--
NOTICE:  Pages 6: Changed 0, Reapped 1, Empty 0, New 0; Tup 422: Vac 7, Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 97,
MaxLen97; Re-using: Free/Avail. Space 3080/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
 
NOTICE:  Index pg_attribute_attrelid_index: Pages 4; Tuples 422: Deleted 7. Elapsed 0/0 sec.
[ etc etc etc ]

What error do you get exactly?
        regards, tom lane

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

От
The Hermit Hacker
Дата:
Odd...I must have typ'd something wrong the last time, cause now it works
for me too *sigh*  

On Sat, 18 Sep 1999, Tom Lane wrote:

> The Hermit Hacker <scrappy@hub.org> writes:
> > 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?
> 
> ???  Works for me ... in fact that's how I usually run vacuum:
> 
> play=> vacuum verbose analyze;
> NOTICE:  --Relation pg_type--
> NOTICE:  Pages 2: Changed 0, Reapped 1, Empty 0, New 0; Tup 114: Vac 1, Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 109,
MaxLen109; Re-using: Free/Avail. Space 3076/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
 
> NOTICE:  Index pg_type_typname_index: Pages 2; Tuples 114: Deleted 1. Elapsed 0/0 sec.
> NOTICE:  Index pg_type_oid_index: Pages 2; Tuples 114: Deleted 1. Elapsed 0/0 sec.
> NOTICE:  --Relation pg_attribute--
> NOTICE:  Pages 6: Changed 0, Reapped 1, Empty 0, New 0; Tup 422: Vac 7, Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 97,
MaxLen97; Re-using: Free/Avail. Space 3080/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
 
> NOTICE:  Index pg_attribute_attrelid_index: Pages 4; Tuples 422: Deleted 7. Elapsed 0/0 sec.
> [ etc etc etc ]
> 
> What error do you get exactly?
> 
>             regards, tom lane
> 

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

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

От
Bruce Momjian
Дата:
> 
> 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?

Worked here:
vacuum verbose analyze pg_class;

> 
> 
> 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 
> 
> 
> ************
> 
> 


--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026