From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gregory S. Williamson <gsw@globexplorer.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: vacuum can't find clog
Date: Sat, 01 Jul 2006 10:28:21 -0400
Message-ID: <23913.1151764101@sss.pgh.pa.us> (raw)
In-Reply-To: <71E37EF6B7DCC1499CEA0316A256832802B3E1DE@loki.wc.globexplorer.net>
References: <71E37EF6B7DCC1499CEA0316A256832802B3E1DE@loki.wc.globexplorer.net>
"Gregory S. Williamson" <gsw@globexplorer.com> writes:
> INFO: vacuuming "public.weekly_log_data"
> ERROR: could not access status of transaction 1081340514
> DETAIL: could not open file "/data/postgres/psql8_test/pg_clog/0407": No such file or directory
This is a data-corruption problem, ie, something has stomped on the xmin
or xmax field of a tuple. (It may or may not be relevant that the high
order half of that number looks like ASCII "s@" ...) Since xmin/xmax
are the first fields looked at that can be checked with any specificity,
"could not access status of transaction" is a common symptom even when
most of a page has been trashed :-(
I don't recall whether we've fixed any bugs post-8.0.3 that might
explain this. My experience is that if you inquire in any detail
you tend to find symptoms that look more like OS- or hardware-level
problems than anything that looks like it could have come from a
Postgres bug ... for instance, I recall finding a block of mail-message
text smack in the middle of a Postgres file in one case.
If you care to investigate exactly what happened, you could break out
pg_filedump and other implements of destruction and see if you can
determine exactly what's bogus in that table. You could probably
also recover whatever data hasn't been overwritten, but the extent
of damage is impossible to guess at this point.
Otherwise, you might just consider this a wake-up call to update your
Postgres and kernel, and maybe run some memory and disk testing.
regards, tom lane
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: tgl@sss.pgh.pa.us, gsw@globexplorer.com
Subject: Re: vacuum can't find clog
In-Reply-To: <23913.1151764101@sss.pgh.pa.us>
References: <71E37EF6B7DCC1499CEA0316A256832802B3E1DE@loki.wc.globexplorer.net> <23913.1151764101@sss.pgh.pa.us>
* 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