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. ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
