From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Eric Renard <dawmette(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Is my db dead ? |
Date: | 2008-02-05 19:47:31 |
Message-ID: | 20080205194731.GC6483@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Eric Renard escribió:
> pg_dump: Error message from server: ERROR: could not access status of
> transaction 3270404
> DETAIL: could not open file "pg_clog/0003": No such file or directory
> pg_dump: The command was: SELECT tableoid, oid, proname, prolang, pronargs,
> proargtypes, prorettype, proacl, pronamespace, (SELECT rolname FROM
> pg_catalog.pg_roles WHERE oid = proowner) as rolname FROM pg_proc WHERE NOT
> proisagg AND pronamespace != (select oid from pg_namespace where nspname =
> 'pg_catalog')
> pg_dumpall: pg_dump failed on database "postgres", exiting
>
> I read about things like zeroing missing pg_clog files... Can it work ? I
> thought clog files were about transactions, but I don't care about last
> transactions, even data from 1 month ago would be enough for me.
> So what can I do from there ?
Before you start randomly zeroing stuff, do you have any files in
pg_clog? What does that directory look like?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-02-05 19:56:46 | Re: Lets get the 8.3 Announcement on the front page of Digg |
Previous Message | Wade Hampton | 2008-02-05 19:41:41 | Issue with Centos 5, Postgres 8.3 (RHEL5 build), timezones |