Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id CE500632D76
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 12 Aug 2010 18:55:11 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024)
	with ESMTP id 57596-01; Thu, 12 Aug 2010 21:55:03 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 78286632D13;
	Thu, 12 Aug 2010 18:55:04 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o7CLsn3o006820;
	Thu, 12 Aug 2010 17:54:49 -0400 (EDT)
To: Robert Haas <robertmhaas@gmail.com>,
 Alanoly Andrews <alanolya@invera.com>,
	Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>,
	"pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] postgres 9.0 crash when bringing up hot standby 
In-reply-to: <6546.1281649220@sss.pgh.pa.us> 
References: <09B23E7BF70425478C1330D893A722C602FEC019BD@MailSVR.invera.com>
	<AANLkTinbaJ3mZ+W5HiYAc+C5ez-pOUFUt+_ajeSsbG26@mail.gmail.com>
	<4C5C6853.40301@enterprisedb.com>
	<AANLkTin9XNVKDGdqDFN8dqaczjey-5NPD44em3N87CVP@mail.gmail.com>
	<09B23E7BF70425478C1330D893A722C602FEC019C6@MailSVR.invera.com>
	<AANLkTikLeGZ3gXrfhzL1x_ysaXko8yPanuOW4cs5rjf5@mail.gmail.com>
	<AANLkTimEHhWGa1JN6FBtY+pzXKSKzKb-MuaXgsDuPW96@mail.gmail.com>
	<6546.1281649220@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Thu, 12 Aug 2010 17:40:20 -0400"
Date: Thu, 12 Aug 2010 17:54:49 -0400
Message-ID: <6819.1281650089@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201008/101
X-Sequence-Number: 35350

I wrote:
> I wonder if the problem is not so much libpqwalreceiver as the
> walreceiver process.  Maybe an ordinary backend process does some
> prerequisite initialization that walreceiver is missing.  Hard to
> guess what, though ... I can't think of anything dlopen() depends on
> that should be under our control.

Actually, that idea is easily tested: try doing
	LOAD 'libpqwalreceiver';
in a regular backend process.

If that still crashes, it might be useful to truss or strace the backend
while it runs the command, and compare that to the trace of
	LOAD 'dblink';

			regards, tom lane