Received: from magus.postgresql.org ([87.238.57.229])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ringerc@ringerc.id.au>) id 1TQC22-0005r6-D3
	for pgsql-general@postgresql.org; Mon, 22 Oct 2012 07:02:38 +0000
Received: from mail-pb0-f46.google.com ([209.85.160.46])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ringerc@ringerc.id.au>) id 1TQC1v-0003mA-5J
	for pgsql-general@postgresql.org; Mon, 22 Oct 2012 07:02:36 +0000
Received: by mail-pb0-f46.google.com with SMTP id rr4so1780749pbb.19
	for <pgsql-general@postgresql.org>;
	Mon, 22 Oct 2012 00:02:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:x-enigmail-version:content-type
	:content-transfer-encoding:x-gm-message-state;
	bh=azX6bDfAFJsmwCyabqtwHI5yhLodTYlSGjLhDR+b5No=;
	b=PYaFjluH3kxme3coG1oAFrOyuhMlV4Zrz9BFe8PE1gVor94F9BZdpOWocZecmSz/WM
	6dr7v9ReDEck1RYZaG7NCJ2/z61Fw4kuPFxl3TafwsN2maAQB2h9GoWFVeApDG16r4i4
	E/cUn6mARoneH0UkmlTgdtrxwdaXxs8pNJGDN8WZnzhtzwwY6KK81q9sYveX9byoD0yR
	Zw728f7a9fa+YBPsQOqQxRAs+o3SlIhbxko8zTWFJbP3NnxkUXFVI52UisYM/kI0Nn+x
	6LEXd/wOe188XtRG9bmd77IBD5kpCRX2AOlRwgnVL0V/tXchwp3cBXLLu3+P2Sp/voeq
	MERg==
Received: by 10.66.78.4 with SMTP id x4mr23575396paw.60.1350889347831;
	Mon, 22 Oct 2012 00:02:27 -0700 (PDT)
Received: from ayaki.localdomain (office1.postnewspapers.com.au.
	[150.101.171.128])
	by mx.google.com with ESMTPS id vi9sm5487199pbc.41.2012.10.22.00.02.24
	(version=SSLv3 cipher=OTHER); Mon, 22 Oct 2012 00:02:26 -0700 (PDT)
Message-ID: <5084EF7E.5080809@ringerc.id.au>
Date: Mon, 22 Oct 2012 15:02:22 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:16.0) Gecko/20121016 Thunderbird/16.0.1
MIME-Version: 1.0
To: raghu ram <raghuchennuru@gmail.com>
CC: pgsql-admin@postgresql.org, pgsql-general <pgsql-general@postgresql.org>
Subject: Re: Streaming Replication Server Crash
References: 
 <CALnrrJQ81icyt7EpzPwPuXPK0SbSv4+C8uyA=6Nwqh+mLw2hOw@mail.gmail.com>
In-Reply-To: 
 <CALnrrJQ81icyt7EpzPwPuXPK0SbSv4+C8uyA=6Nwqh+mLw2hOw@mail.gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: 
 ALoCoQl+OOIjz0Hu7ZuDLXbK+eQKmn4vBay5wPOmFjYZzEkWuarVd5k14PuuDU/WQ5DtgYT3hr88
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201210/652
X-Sequence-Number: 191620

On 10/19/2012 04:40 PM, raghu ram wrote:
> Hi All,
> 
> We have configured Streaming Replication b/w Primary and Standby server
> and Pgpool-II load balancing module diverting
> SELECT statements to  Standby server. As per our observations, Standby
> server crashed during peak hours on today and error message as follows

> 2012-10-19 12:26:46 IST [1338]: [18-1] user=,db= LOG:  server process
> (PID 15565) was terminated by signal 10
> 
> 2012-10-19 12:26:46 IST [1338]: [19-1] user=,db= LOG:  terminating any
> other active server processes

That's odd. SIGUSR1 (signal 10) shouldn't terminate PostgreSQL.

Was the server intentionally sent SIGUSR1 by an admin? Do you know what
triggered the signal?

Are you running any procedural languages other than PL/PgSQL, or any
custom C extensions? Anything that might have unwittingly cleared the
signal handler for SIGUSR1?

--
Craig Ringer