Tom Lane wrote:
> Steve Singer <ssinger@ca.afilias.info> 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