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: Tue, 27 Jan 2004 13:41:45 -0800
Message-ID: <004601c3e51e$5c750ba0$0b00a8c0@amer.cisco.com> (raw)
In-Reply-To: <28344.1075238139@sss.pgh.pa.us>

Cut and pasted from my screen to the e-mail. I did shutdown postmaster
prior to running postgres standalone. I assume that quit from postgres
backend stops it. I did restart postmaster prior running the psql vacuum
full. 

Sorry, forgot to run verbose mode on the commands. I have re-initialized
the DB and restored from a backup. Will send info if it happens again.

Thanks for the help

Chris

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
Sent: Tuesday, January 27, 2004 1:16 PM
To: cjwhite@cisco.com
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table 


"Chris White \(cjwhite\)" <cjwhite@cisco.com> writes:
> Here is the info. I am running 7.2.1.

7.2.1 is a bit long in the tooth; you really ought to be running 7.2.4
if you are still in the 7.2 series.  However I don't think that has much
to do with your immediate problem.

The only thing that struck me about your transcript is that you didn't
show shutting down and restarting the postmaster.  You didn't try to run
a standalone backend concurrently with the postmaster did you?  (There
are supposed to be interlocks against that, but maybe they failed.) The
failures sort of look like the standalone backend's changes did not
completely propagate back to the regular database, and that's the only
very plausible mechanism I can think of for that ...

Also, I really wanted to see the output of vacuum verbose.  Just
"vacuum" doesn't tell anything much.

			regards, tom lane




view thread (14+ messages)  latest in thread

Message-ID: <004601c3e51e$5c750ba0$0b00a8c0@amer.cisco.com>
Permalink:  ../004601c3e51e$5c750ba0$0b00a8c0@amer.cisco.com/
Also on:    postgresql.org/message-id/004601c3e51e$5c750ba0$0b00a8c0@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: <004601c3e51e$5c750ba0$0b00a8c0@amer.cisco.com>
  References: <28344.1075238139@sss.pgh.pa.us> <004601c3e51e$5c750ba0$0b00a8c0@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