pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Edoardo Ceccarelli <eddy@axa.it>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_clog
Date: Mon, 18 Dec 2006 20:01:17 +0100
Message-ID: <2c5b22d10612181101r3c0ca187qac319f41587cec2a@mail.gmail.com> (raw)
In-Reply-To: <25199.1166467713@sss.pgh.pa.us>
References: <2c5b22d10612180957s78fa6fd8s9f913673bfadbe0e@mail.gmail.com>
	<25199.1166467713@sss.pgh.pa.us>

Thanks, I tought about that as well but with PG7.X we had the same machine
with the same database running smoothly for more than a year
now strange things like this are happening:

2006-12-18 14:49:35 CET [14691]  : LOG:  server process (PID 13421)
wasterminated by signal 11
2006-12-18 14:49:35 CET [14691]  : LOG:  terminating any other active
serverprocesses
2006-12-18 14:49:35 CET [14009] db idle: WARNING:  terminating connection
because of crash of another server process
2006-12-18 14:49:35 CET [14009] db idle: DETAIL:  The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server process exited abnormally and possibly corrupted
shared memory.
2006-12-18 14:49:35 CET [14009] db idle: HINT:  In a moment you should be
able to reconnect to the database and repeat your command.

I bet a crashing process could cause that data corruption, right?


On 12/18/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> "Edoardo Ceccarelli" <eddy@axa.it> writes:
> > pg_dump: ERROR:  could not access status of transaction 1629514106
> > DETAIL:  could not open file "pg_clog/0612": No such file or directory
>
> This looks like a data corruption problem to me.  It may or may not be
> significant that 1629514106 = 0x6120697a = ASCII 'zi a' (or 'a iz' if
> you are on a big-endian machine).  That looks at least a little bit
> plausible for Italian text, so I'm wondering if your disk drive or OS
> has hiccuped and dumped a sector or two of some other file into your
> database :-(.  We've seen it happen before.
>
> Check the archives for past discussions about locating and recovering
> from corrupted data.
>
>                         regards, tom lane
>

view thread (7+ messages)  latest in thread

Message-ID: <2c5b22d10612181101r3c0ca187qac319f41587cec2a@mail.gmail.com>
Permalink:  ../2c5b22d10612181101r3c0ca187qac319f41587cec2a@mail.gmail.com/
Also on:    postgresql.org/message-id/2c5b22d10612181101r3c0ca187qac319f41587cec2a@mail.gmail.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: eddy@axa.it, tgl@sss.pgh.pa.us
  Subject: Re: pg_clog
  In-Reply-To: <2c5b22d10612181101r3c0ca187qac319f41587cec2a@mail.gmail.com>
  References: <2c5b22d10612180957s78fa6fd8s9f913673bfadbe0e@mail.gmail.com> <25199.1166467713@sss.pgh.pa.us> <2c5b22d10612181101r3c0ca187qac319f41587cec2a@mail.gmail.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