Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id AA0EC632875 for ; Wed, 25 Aug 2010 12:45:43 -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 71822-05 for ; Wed, 25 Aug 2010 15:45:36 +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 5E33A632904 for ; Wed, 25 Aug 2010 12:45:36 -0300 (ADT) Received: from ms5.yyz2.afilias-ops.info ([10.50.129.111] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from ) id 1OoIAR-0005Hy-6k; Wed, 25 Aug 2010 15:45:35 +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 1OoIAQ-00030B-6B; Wed, 25 Aug 2010 15:45:34 +0000 Message-ID: <4C753A9E.6020503@ca.afilias.info> Date: Wed, 25 Aug 2010 11:45:34 -0400 From: Steve Singer User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Steve Singer CC: Tom Lane , PostgreSQL-development Hackers Subject: Re: HS/SR on AIX References: <4C743C2D.1060209@ca.afilias.info> <8446.1282694191@sss.pgh.pa.us> <4C753155.3070708@ca.afilias.info> In-Reply-To: <4C753155.3070708@ca.afilias.info> 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/1817 X-Sequence-Number: 168620 Steve Singer wrote: > Tom Lane wrote: >> Steve Singer writes: >>> I think I've been able to reproduce the issue floating around with >>> streaming replication 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. > A clean build from the beta4 source tarball where I'm careful to install into a clean (ie no old beta2 artifacts laying around waiting to be overwritten) isn't reproducing the issue. I'm happy to try other things if people suggest them (or if the original reporter is still getting this after making sure he cleans up old files first) but I'm thinking that was the issue. -- Steve Singer Afilias Canada Data Services Developer 416-673-1142