Re: Error seen when vacuuming pg_largeobject table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: cjwhite(at)cisco(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Error seen when vacuuming pg_largeobject table
Date: 2004-01-27 21:15:39
Message-ID: 28344.1075238139@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Chris White (cjwhite) 2004-01-27 21:41:45 Re: Error seen when vacuuming pg_largeobject table
Previous Message Gaetano Mendola 2004-01-27 19:06:42 Postgres 7.3.5