Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id D0414634420 for ; Wed, 25 Aug 2010 12:06:15 -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 21154-01-3 for ; Wed, 25 Aug 2010 15:06:08 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by mail.postgresql.org (Postfix) with ESMTP id 0857363348B for ; Wed, 25 Aug 2010 12:05:58 -0300 (ADT) Received: from ms6.yyz2.afilias-ops.info ([10.50.129.112] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from ) id 1OoHY6-0004WG-42; Wed, 25 Aug 2010 15:05:58 +0000 Received: from tor-gateway.afilias.info ([199.15.87.4] helo=[10.10.46.23]) by smtp.afilias.info with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1OoHY6-0003Io-6i; Wed, 25 Aug 2010 15:05:58 +0000 Message-ID: <4C753155.3070708@ca.afilias.info> Date: Wed, 25 Aug 2010 11:05:57 -0400 From: Steve Singer User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Tom Lane CC: PostgreSQL-development Hackers Subject: Re: HS/SR on AIX References: <4C743C2D.1060209@ca.afilias.info> <8446.1282694191@sss.pgh.pa.us> In-Reply-To: <8446.1282694191@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.21 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201008/1813 X-Sequence-Number: 168616 Tom Lane wrote: > Steve Singer writes: >> I think I've been able to reproduce the issue floating around with >> streaming replication on AIX. > > Excellent, because we weren't getting much from the original reporter. I'm withdrawing my comment, today on a clean install of the binaries I am not able to reproduce any of this. Today with beta4 I can stream replication to the standby and bring the standby up to read-write without issues. Yesterday when I had put beta4 on top of beta2 without explicitly deleting all of the beta2 binaries/libraries first. I'm thinking maybe some portions of beta2 where still laying around. It is also possible that an old version of a shared library was still sitting in memory and was being picked up by the newer postgresql (man slibclean on AIX) I will do another clean build from the beta4 source tar to confirm that I'm not still having the issue but I'm thinking the original reporter might have done something similar and had some old artifacts laying around. > >> This worked fine with beta2 but now seems to be an issue on beta4. > >> If I do >> export LIBPATH=/opt/dbs/pgsql9-beta2/lib/ >> before starting the standby postmaster then it seems to work. > > Fascinating. That seems to prove that it's an rpath problem. My > first guess is that the relevant change between beta2 and beta4 is > my LDFLAGS changes. See > http://archives.postgresql.org/pgsql-committers/2010-07/msg00060.php > and following commits. > > regards, tom lane > -- Steve Singer Afilias Canada Data Services Developer 416-673-1142