From: | "Shoaib Mir" <shoaibmir(at)gmail(dot)com> |
---|---|
To: | "Edoardo Ceccarelli" <eddy(at)axa(dot)it> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_clog |
Date: | 2006-12-18 18:09:25 |
Message-ID: | bf54be870612181009k298f03a3s26a80b60fd3d72e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-jdbc |
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(at)axa(dot)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;
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Edoardo Ceccarelli | 2006-12-18 18:26:44 | Re: pg_clog |
Previous Message | Edoardo Ceccarelli | 2006-12-18 18:04:33 | Re: pg_clog |
From | Date | Subject | |
---|---|---|---|
Next Message | Edoardo Ceccarelli | 2006-12-18 18:26:44 | Re: pg_clog |
Previous Message | Edoardo Ceccarelli | 2006-12-18 18:04:33 | Re: pg_clog |