Skip site navigation (1) Skip section navigation (2)

Re: Error seen when vacuuming pg_largeobject table

From: "Chris White (cjwhite)" <cjwhite(at)cisco(dot)com>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Error seen when vacuuming pg_largeobject table
Date: 2004-01-29 17:03:35
Message-ID: 006501c3e689$d6f00cb0$57976b80@amer.cisco.com (view raw or flat)
Thread:
Lists: pgsql-admin
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


In response to

Responses

pgsql-admin by date

Next:From: Tom LaneDate: 2004-01-29 17:11:51
Subject: Re: How to use int2vector
Previous:From: Tom LaneDate: 2004-01-29 16:32:29
Subject: Re: Routine maintenance - vacuum, analyse and autovacuum

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group