Re: Error seen when vacuuming pg_largeobject table

Tom,

It happened again. After doing the reindex, I did a vacuum full on the
pg_largeobject table. This time I did not get the TUPLE INDEX error but
the server terminated at the end of the vacuum command. The backend is
still running even though I get the error message:

aesop=# vacuum full verbose pg_largeobject;
NOTICE: --Relation pg_largeobject-- blocks 21
NOTICE: Pages 21: Changed 0, reaped 19, Empty 0, New 0; Tup 69: Vac
749, Keep/VTL 0/0, UnUsed 181, MinLen 16, MaxLen 2092; Re-using:
Free/Avail. Space 146752/146752; EndEmpty/Avail. Pages 0/21.
CPU 0.00s/0.00u sec elapsed 0.00 sec.
NOTICE: Index pg_largeobject_loid_pn_index: Pages 2; Tuples 69: Deleted
0.
CPU 0.00s/0.00u sec elapsed 0.00 sec.
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.

It consistently happens when I try to vacuum full the pg_largeobject
table. Is there anything I can get from the system to determine what is
happening?
Chris

-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: Wednesday, January 28, 2004 11:52 AM
To: cjwhite(at)cisco(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table

> Got it to happen again after a power fail. Here is the logs this time
> with verbose.

Hm, those backend crashes should have left core dumps; can you get a
stack trace from the core?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html