Hello Pavel,
Thanks for the info, this is very great help.
Regard
Louis



----- Original Message ----
From: Pavel Stehule <pavel.stehule@gmail.com>
To: mailtolouis2020-postgres@yahoo.com
Cc: Postgres <pgsql-general@postgresql.org>
Sent: Thursday, May 15, 2008 4:43:36 AM
Subject: Re: [GENERAL] postgres crash when select a record

Hello

2008/5/14* <mailtolouis2020-postgres@yahoo.com>:
> Hello,
>
> Yes, I deleted that record, and now my backup is working fine! Thanks
>
> But why this problem came out? Is there anyway to trace it down and how it
> happen? Or is it a bug of postgres?
>

I can't to eliminate PostgreSQL bug, but sometimes this problem
signalize hw problems. You can search in archive similar cases.
Postgres crashes, because stored row are in brokenformat. There are
some projects that would solve it better -
http://svana.org/kleptog/pgsql/pgfsck.html

Regards
Pavel Stehule

> Regards
> Louis
>
> ----- Original Message ----
> From: Pavel Stehule <pavel.stehule@gmail.com>
> To: mailtolouis2020-postgres@yahoo.com
> Cc: Postgres <pgsql-general@postgresql.org>
> Sent: Wednesday, May 14, 2008 6:13:05 PM
> Subject: Re: [GENERAL] postgres crash when select a record
>
> Hello
>
> Delete this broken row
>
> Regards
> Pavel Stehule
>
> 2008/5/14* <mailtolouis2020-postgres@yahoo.com>:
>> Hello,
>>
>> I wish some could help me on this.
>>
>> I got a table which has 100500 records, when I try to query this
>> particular
>> record
>>
>> select * from cs_sr_mthly_rtn where mthly_rtn_id = 61609;
>> Postgres crash, and show this errors:
>>
>> server closed the connection unexpectedly
>>* This probably means the server terminated abnormally
>>* before or while processing the request.
>>
>> And in the serverlog, it shows:
>>
>> LOG:* server process (PID 395) was terminated by signal 11
>> LOG:* terminating any other active server processes
>> FATAL:* the database system is in recovery mode
>> LOG:* all server processes terminated; reinitializing
>> LOG:* database system was interrupted at 2008-05-14 12:52:15 BST
>> LOG:* checkpoint record is at 0/48DEC034
>> LOG:* redo record is at 0/48DEC034; undo record is at 0/0; shutdown TRUE
>> LOG:* next transaction ID: 0/705241; next OID: 49152
>> LOG:* next MultiXactId: 1; next MultiXactOffset: 0
>> LOG:* database system was not properly shut down; automatic recovery in
>> progress
>> LOG:* redo starts at 0/48DEC07C
>> LOG:* unexpected pageaddr 0/433AC000 in log file 0, segment 74, offset
>> 3850240
>> LOG:* redo done at 0/4A3ABFC0
>> LOG:* database system is ready
>>
>> Because of this,I'm not able to do pg_dump backup anymore.
>>
>> Anyone can help me tosolve this problem?
>>
>>
>> Thanks
>> louis
>

Definitely run some tests on the hardware, like memtest86, and some
drive tests for bad blocks.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general