Thanks Tom .

When I did.... Is there any that I can run some commands to point it
to *libpq.so.5.
  I have  LD_LIBRARY_PATH =/opt/postgres/9.0.2/lib. still it is pointing to
** /usr/lib  .. Any suggestions? *

*ldd libpqwalreceiver.so*

 * libpq.so.4 =>    /usr/lib/libpq.so.4*
*        libgcc_s.so.1 =>         /usr/sfw/lib/libgcc_s.so.1*
*        libssl.so.0.9.7 =>       /usr/sfw/lib/libssl.so.0.9.7*
*        libcrypto.so.0.9.7 =>    /usr/sfw/lib/libcrypto.so.0.9.7*
*        libresolv.so.2 =>        /usr/lib/libresolv.so.2*
*        libsocket.so.1 =>        /usr/lib/libsocket.so.1*
*        libnsl.so.1 =>   /usr/lib/libnsl.so.1*
*        libpthread.so.1 =>       /usr/lib/libpthread.so.1*
*        libc.so.1 =>     /lib/libc.so.1*
*        libmp.so.2 =>    /lib/libmp.so.2*
*        libmd.so.1 =>    /lib/libmd.so.1*
*        libscf.so.1 =>   /lib/libscf.so.1*
*        libdoor.so.1 =>  /lib/libdoor.so.1*
*        libuutil.so.1 =>         /lib/libuutil.so.1*
*        libgen.so.1 =>   /lib/libgen.so.1*
*        libssl_extra.so.0.9.7 =>         /usr/sfw/lib/libssl_extra.so.0.9.7
*
*        libcrypto_extra.so.0.9.7 =>
 /usr/sfw/lib/libcrypto_extra.so.0.9.7*
*        libm.so.2 =>     /lib/libm.so.2*
*        /platform/SUNW,SPARC-Enterprise/lib/libc_psr.so.1*


Appreciate your help

Regards

On Sat, Jun 11, 2011 at 12:25 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:

> akp geek <akpg...@gmail.com> writes:
> >          After making the required changes to the Primary and slave , I
> have
> > restarted the slave and I keep seeing the following in the logs.
>
> > *FATAL:  could not connect to the primary server: invalid connection
> option
> > "replication"*
>
> That message has to be caused by libpq, because the string 'invalid
> connection option' occurs nowhere else in PG.  I am guessing that you
> have an 8.4 or older libpq.so that walreceiver.so is somehow linking to.
> I don't know what Solaris' equivalent of LD_LIBRARY_PATH is, but I'd be
> looking into that angle if I were you.
>
>                        regards, tom lane
>

Reply via email to