From: Bruce Momjian <pgman@candle.pha.pa.us>
To: codeWarrior <gpatnude@hotmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Urgent!
Date: Thu, 13 Oct 2005 11:56:48 -0400 (EDT)
Message-ID: <200510131556.j9DFumT03567@candle.pha.pa.us> (raw)
In-Reply-To: <dilui9$uv9$1@news.hub.org>
codeWarrior wrote:
> 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...
PostgreSQL should never get corrupted by turning off the server. It
isn't ideal to do that, but it should not get corrupted.
---------------------------------------------------------------------------
>
> 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@workskillsprofessionals.com.au> wrote in message
> news:221385EC3F18A44DB0925467A1D2395F38FB07@exsrv3.workskillsprofessionals.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
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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: pgman@candle.pha.pa.us, gpatnude@hotmail.com
Subject: Re: Urgent!
In-Reply-To: <200510131556.j9DFumT03567@candle.pha.pa.us>
References: <dilui9$uv9$1@news.hub.org> <200510131556.j9DFumT03567@candle.pha.pa.us>
* 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