pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pieter-Jan Savat <pieterjan.savat@barclab.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Memory/Performance issue: server closed the connection
Date: Tue, 11 Oct 2005 17:53:07 +0200
Message-ID: <434BDFE3.6040705@barclab.com> (raw)
In-Reply-To: <13658.1129038551@sss.pgh.pa.us>
References: <434B9169.6040404@barclab.com>
	<13658.1129038551@sss.pgh.pa.us>



Tom Lane wrote:

>That shouldn't happen.  What shows up in the postmaster log? 
>
Here is the output of the log:

2005-10-11 17:22:00 CEST (@) [] DEBUG:  checkpoint complete; 0 
transaction log file(s) added, 0 removed, 3 recycled
2005-10-11 17:22:26 CEST (@) [] LOG:  checkpoints are occurring too 
frequently (27 seconds apart)
2005-10-11 17:22:26 CEST (@) [] HINT:  Consider increasing the 
configuration parameter "checkpoint_segments".
2005-10-11 17:22:26 CEST (@) [] DEBUG:  checkpoint starting
2005-10-11 17:22:27 CEST (@) [] DEBUG:  checkpoint complete; 0 
transaction log file(s) added, 0 removed, 3 recycled
2005-10-11 17:22:28 CEST ([unknown]@[unknown]) [2005-10-11 17:22:28 
CEST] LOG:  incomplete startup packet
2005-10-11 17:22:28 CEST (postgres@TheCore) [2005-10-11 17:08:49 CEST] 
PANIC:  right sibling's left-link doesn't match
2005-10-11 17:22:28 CEST (postgres@TheCore) [2005-10-11 17:08:49 CEST] 
STATEMENT:  update aaa set blinding_flag = 'D' where study_id = 144
2005-10-11 17:22:28 CEST (@) [] LOG:  server process (PID 13726) was 
terminated by signal 6
2005-10-11 17:22:28 CEST (@) [] LOG:  terminating any other active 
server processes
2005-10-11 17:22:28 CEST (postgres@TheCore) [2005-10-11 17:08:48 CEST] 
WARNING:  terminating connection because of crash of another server process
2005-10-11 17:22:28 CEST (postgres@TheCore) [2005-10-11 17:08:48 CEST] 
DETAIL:  The postmaster has commanded this server process to roll back 
the current tran
saction and exit, because another server process exited abnormally and 
possibly corrupted shared memory.
2005-10-11 17:22:28 CEST (postgres@TheCore) [2005-10-11 17:08:48 CEST] 
HINT:  In a moment you should be able to reconnect to the database and 
repeat your comm
and.
2005-10-11 17:22:28 CEST (postgres@template1) [2005-10-11 17:08:48 CEST] 
WARNING:  terminating connection because of crash of another server process
2005-10-11 17:22:28 CEST (postgres@template1) [2005-10-11 17:08:48 CEST] 
DETAIL:  The postmaster has commanded this server process to roll back 
the current tr
ansaction and exit, because another server process exited abnormally and 
possibly corrupted shared memory.
2005-10-11 17:22:28 CEST (postgres@template1) [2005-10-11 17:08:48 CEST] 
HINT:  In a moment you should be able to reconnect to the database and 
repeat your co
mmand.
2005-10-11 17:22:28 CEST (@) [] LOG:  all server processes terminated; 
reinitializing
2005-10-11 17:22:28 CEST (@) [] LOG:  database system was interrupted at 
2005-10-11 17:22:27 CEST
2005-10-11 17:22:28 CEST (@) [] LOG:  checkpoint record is at B/FB02FD7C
2005-10-11 17:22:28 CEST (@) [] LOG:  redo record is at B/FB008754; undo 
record is at 0/0; shutdown FALSE
2005-10-11 17:22:28 CEST (@) [] LOG:  next transaction ID: 4546927; next 
OID: 83401
2005-10-11 17:22:28 CEST (@) [] LOG:  database system was not properly 
shut down; automatic recovery in progress
2005-10-11 17:22:28 CEST (@) [] LOG:  redo starts at B/FB008754
2005-10-11 17:22:28 CEST (@) [] LOG:  unexpected pageaddr B/F4150000 in 
log file 11, segment 251, offset 1376256
2005-10-11 17:22:28 CEST (@) [] LOG:  redo done at B/FB14FF98
2005-10-11 17:22:28 CEST (@) [] LOG:  database system is ready
2005-10-11 17:22:48 CEST ([unknown]@[unknown]) [2005-10-11 17:22:48 
CEST] LOG:  incomplete startup packet

> If the server is dumping core, can you get a stack trace from it?
>  
>
I can't find any special file in /pgdb/system/base or its subdirectories.



view thread (6+ messages)  latest in thread

Message-ID: <434BDFE3.6040705@barclab.com>
Permalink:  ../434BDFE3.6040705@barclab.com/
Also on:    postgresql.org/message-id/434BDFE3.6040705@barclab.com

 · 

reply

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: pieterjan.savat@barclab.com, tgl@sss.pgh.pa.us
  Subject: Re: Memory/Performance issue: server closed the connection
  In-Reply-To: <434BDFE3.6040705@barclab.com>
  References: <434B9169.6040404@barclab.com> <13658.1129038551@sss.pgh.pa.us> <434BDFE3.6040705@barclab.com>

* 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