Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id B87A5632D76
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 12 Aug 2010 18:40:32 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024)
	with ESMTP id 53421-02; Thu, 12 Aug 2010 21:40:24 +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 72CFF632563;
	Thu, 12 Aug 2010 18:40:25 -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 o7CLeK1B006547;
	Thu, 12 Aug 2010 17:40:20 -0400 (EDT)
To: Robert Haas <robertmhaas@gmail.com>
cc: 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: <AANLkTimEHhWGa1JN6FBtY+pzXKSKzKb-MuaXgsDuPW96@mail.gmail.com> 
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>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Thu, 12 Aug 2010 16:37:50 -0400"
Date: Thu, 12 Aug 2010 17:40:20 -0400
Message-ID: <6546.1281649220@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/100
X-Sequence-Number: 35349

Robert Haas <robertmhaas@gmail.com> writes:
> Per off-list discussion with Alanoly, we've determined the following:

> dblink was compiled with the same flags as libpqwalreciever
> dblink works
> libpqwalreceiver crashes

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.

			regards, tom lane