pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shoaib Mir <shoaibmir@gmail.com>
To: Edoardo Ceccarelli <eddy@axa.it>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_clog
Date: Mon, 18 Dec 2006 23:09:25 +0500
Message-ID: <bf54be870612181009k298f03a3s26a80b60fd3d72e@mail.gmail.com> (raw)
In-Reply-To: <2c5b22d10612180957s78fa6fd8s9f913673bfadbe0e@mail.gmail.com>
References: <2c5b22d10612180957s78fa6fd8s9f913673bfadbe0e@mail.gmail.com>

You can try creating the missing clog file as 256K of zeros, once that is
done you can now try going through the pg_dump process again.

This suggestion might help you as well -->
http://archives.postgresql.org/pgsql-admin/2003-02/msg00263.php

---------------------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 12/18/06, Edoardo Ceccarelli <eddy@axa.it> wrote:
>
> Hi,
>
> just encountered this error trying to dump my db:
> any ideas?
>
> Thank you
>
>
> pg_dump: ERROR:  could not access status of transaction 1629514106
>
> DETAIL:  could not open file "pg_clog/0612": No such file or directory
>
> pg_dump: SQL command to dump the contents of table "annuncio400" failed:
> PQendcopy() failed.
>
> pg_dump: Error message from server: ERROR:  could not access status of
> transaction 1629514106
>
> DETAIL:  could not open file "pg_clog/0612": No such file or directory
>
> pg_dump: The command was: COPY public.annuncio400 (testo, telef1, pref1,
> rubric, tiprec, uscita, telef2, pref2, giornouscita, meseuscita, annouscita,
> prezzo, annofabbr, locali, codedi, codcliente, email, tipoannuncio, ka) TO
> stdout;
>
>

view thread (7+ messages)  latest in thread

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