I've been through a similar situation before (partition was full, and subsequently, PG wasn't able to access a pg_clog/<one file>. Tom Lane had referred me to another archive about zeroing out that particular file, which had worked for me and the database was up. And yes, don't shutdown the machine like that. Thanks, Anjan -----Original Message----- From: codeWarrior [mailto:gpatnude@xxxxxxxxxxx] Sent: Thursday, October 13, 2005 11:31 AM To: pgsql-admin@xxxxxxxxxxxxxx Subject: Re: Urgent! Lookas as if you've managed to turn off your computer mid-transaction thereby corrupting the postgreSQL commit logs (pg_clog)... You should never just turn off a database server... always shut it down normally... Turning it off was a major mistake. I dont know if you can recover or not as the system (postgreSQL) now thinks it is in the middle of a transaction... As far as recovery goes... You might try a vacuum full and pg_resetxlog (search the postgreSQL docs for pg_resetxlog)... Other than that you might need to get Tom Lane's attention on this one... ""Nirav Parikh"" <nirav.p@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:221385EC3F18A44DB0925467A1D2395F38FB07@xxxxxxxxxxxxxxxxxxxxxxxxxxxx ls.com.au... Hi, I got this error message when I tried to do pg_dump on the database. pg_dump: ERROR: invalid memory alloc request size 4294967293 pg_dump: SQL command to dump the contents of table "wordlist" failed: PQendcopy() failed. pg_dump: Error message from server: ERROR: invalid memory alloc request size 4294967293 pg_dump: The command was: COPY public.wordlist (word_id, word, count_word) TO stdout; I went to phppgadmin and try to access the worldlist table and it also gives me following error message: ERROR: could not access status of transaction 6849340 DETAIL: could not open file "/var/lib/pgsql/data/pg_clog/0006": No such file or directory In statement: SELECT COUNT(*) AS total FROM (SELECT "oid", * FROM "public"."wordlist") AS sub CPU was heating up so I turn off the computer and to fix the problem and after that this occour. I don't know if this has anything to with database corruption. This is production server and I don't have latest backup does anyone how to resolve this. Please Help Regards, Nirav Parikh ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
