Re: Error seen when vacuuming pg_largeobject table

Sorry I meant to say the server terminated the connection as indicated
by the error message but the server is still running and there is no
core (This time I enabled them).

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: Thursday, January 29, 2004 7:10 AM
To: cjwhite(at)cisco(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table

"Chris White \(cjwhite\)" <cjwhite(at)cisco(dot)com> writes:
> 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.

Can you enable core dumps and get a stack trace?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if
your
joining column's datatypes do not match