pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris White (cjwhite) <cjwhite@cisco.com>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Error seen when vacuuming pg_largeobject table
Date: Wed, 28 Jan 2004 22:54:34 -0800
Message-ID: <003901c3e634$c321dc90$57976b80@amer.cisco.com> (raw)
In-Reply-To: <28648.1075319535@sss.pgh.pa.us>

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@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Wednesday, January 28, 2004 11:52 AM
To: cjwhite@cisco.com
Cc: pgsql-admin@postgresql.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




view thread (14+ messages)  latest in thread

Message-ID: <003901c3e634$c321dc90$57976b80@amer.cisco.com>
Permalink:  ../003901c3e634$c321dc90$57976b80@amer.cisco.com/
Also on:    postgresql.org/message-id/003901c3e634$c321dc90$57976b80@amer.cisco.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: cjwhite@cisco.com, tgl@sss.pgh.pa.us
  Subject: Re: Error seen when vacuuming pg_largeobject table
  In-Reply-To: <003901c3e634$c321dc90$57976b80@amer.cisco.com>
  References: <28648.1075319535@sss.pgh.pa.us> <003901c3e634$c321dc90$57976b80@amer.cisco.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox