Re: Postgres process is crashing continously in 9.1.1 - Mailing list pgsql-general

From Jayashankar K B
Subject Re: Postgres process is crashing continously in 9.1.1
Date
Msg-id 1365276B7BDA4C40A519F0B4088230B3098DE9C4@POCITMSEXMB03.LntUniverse.com
Whole thread Raw
In response to Postgres process is crashing continously in 9.1.1  (Jayashankar K B <Jayashankar.KB@lnties.com>)
Responses Re: Postgres process is crashing continously in 9.1.1
List pgsql-general

We can understand the difference in shared buffer size as the Windows PC has 2GB of RAM and the board has 256MB of RAM.

So please let us know if this shared buffer parameter has any relation to the problem we are facing.

 

Thanks and Regards

Jayashankar

 

From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Jayashankar K B
Sent: Tuesday, May 22, 2012 11:27 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Postgres process is crashing continously in 9.1.1

 

Hi,

 

We are using Postgres 9.1.1 on a board with Coldfire controller.

The postgres processes are crashing and restarting upon executing a particular instruction and it keeps repeating. Even when we tried with Postgres 9.1.3, same problem happens.

It works fine until the FINANCIALTRANSACTIONID reaches 1000.

But the same setup is working fine on a windows PC. We have tried to compare the configuration differences between windows PC and the board and found that only difference is the Shared Buffers which is 32 on the PC and 24 on the board.

 

I am pasting the server log from the board here.

The line highlighted in yellow is the instruction which is causing the crash.

Please let us know why this crash is happening and how we can fix it.

 

 

LOG:  redo starts at 0/D9B75B4

LOG:  record with zero length at 0/D9BBE5C

LOG:  redo done at 0/D9BBE22

LOG:  last completed transaction was at log time 2012-05-22 02:22:26.641488+00

LOG:  database system is ready to accept connections

LOG:  autovacuum launcher started

ERROR:  duplicate key value violates unique constraint "financialtransaction_pkey"

DETAIL:  Key (financialtransactionid)=(1004) already exists.

STATEMENT:  Insert into FINANCIALTRANSACTION (ATTENDANT,ENGINEHOUR,RECEIPTPRINTED,FINANCIALTRANSACTIONID) values ('0','0.0','0','1004')

LOG:  server process (PID 4016) was terminated by signal 11: Segmentation fault

LOG:  terminating any other active server processes

WARNING:  terminating connection because of crash of another server process

DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

HINT:  In a moment you should be able to reconnect to the database and repeat your command.

FATAL:  poll() failed in statistics collector: Unknown error 516

LOG:  statistics collector process (PID 3962) exited with exit code 1

LOG:  all server processes terminated; reinitializing

LOG:  database system was interrupted; last known up at 2012-05-22 02:22:29 UTC

LOG:  database system was not properly shut down; automatic recovery in progress

LOG:  consistent recovery state reached at 0/D9BBEAA

LOG:  redo starts at 0/D9BBEAA

LOG:  record with zero length at 0/D9C07FA

LOG:  redo done at 0/D9C07C0

LOG:  last completed transaction was at log time 2012-05-22 02:23:05.372245+00

LOG:  database system is ready to accept connections

LOG:  autovacuum launcher started

ERROR:  duplicate key value violates unique constraint "financialtransaction_pkey"

DETAIL:  Key (financialtransactionid)=(1004) already exists.

STATEMENT:  Insert into FINANCIALTRANSACTION (ATTENDANT,ENGINEHOUR,RECEIPTPRINTED,FINANCIALTRANSACTIONID) values ('0','0.0','0','1004')

LOG:  server process (PID 4098) was terminated by signal 11: Segmentation fault

LOG:  terminating any other active server processes

WARNING:  terminating connection because of crash of another server process

DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

HINT:  In a moment you should be able to reconnect to the database and repeat your command.

FATAL:  poll() failed in statistics collector: Unknown error 516

LOG:  statistics collector process (PID 4035) exited with exit code 1

LOG:  all server processes terminated; reinitializing

LOG:  database system was interrupted; last known up at 2012-05-22 02:23:08 UTC

LOG:  database system was not properly shut down; automatic recovery in progress

LOG:  consistent recovery state reached at 0/D9C0848

LOG:  redo starts at 0/D9C0848

LOG:  record with zero length at 0/D9C5218

LOG:  redo done at 0/D9C51DE

LOG:  last completed transaction was at log time 2012-05-22 02:23:49.659502+00

LOG:  database system is ready to accept connections

LOG:  autovacuum launcher started

 

 

 

Thanks and Regards

Jayashankar

Larsen & Toubro Limited

www.larsentoubro.com

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

 Earth Day. Every Day.

Larsen & Toubro Limited

www.larsentoubro.com

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

 Earth Day. Every Day.

pgsql-general by date:

Previous
From: Greg Simpson
Date:
Subject: Bitrock XML Source
Next
From: John R Pierce
Date:
Subject: Re: Bitrock XML Source