Re: BUG #4667: pg_standby error on Solaris 10 SPARC 64 bin
От | AShved@symcor.com |
---|---|
Тема | Re: BUG #4667: pg_standby error on Solaris 10 SPARC 64 bin |
Дата | |
Msg-id | OFB1C3606D.0205B12B-ON85257562.005DEF87-85257562.005DFD8C@symcor.com обсуждение исходный текст |
Ответ на | Re: BUG #4667: pg_standby error on Solaris 10 SPARC 64 bin (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #4667: pg_standby error on Solaris 10 SPARC 64 bin
Re: BUG #4667: pg_standby error on Solaris 10 SPARC 64 bin |
Список | pgsql-bugs |
I have ./postgres/8.3-community/lib/64/libpq.so.5 so how do i make it use it. Regards, Andrew Shved DBA Symcor Inc, Corporate Applications Tel:(905)273-1433 Mobile:(416)803-2675 "aut viam inveniam aut faciam" Tom Lane <tgl@sss.pgh.pa.u s> To "Andrew Shved" <ashved@symcor.com> 19/02/2009 10:54 cc AM pgsql-bugs@postgresql.org Subject Re: [BUGS] BUG #4667: pg_standby error on Solaris 10 SPARC 64 bin "Andrew Shved" <ashved@symcor.com> writes: > I installed PostgreSQL 8.3.5 from binaries using from > http://www.postgresql.org/ftp/binary/v8.3.5/solaris/solaris10/sparc/ > and I get the following error in my standby log when trying to restore - > ld.so.1: pg_standby: fatal: libpq.so.5: open failed: No such file or > directory Do you have that version of libpq.so installed? If so, is it in a place where programs will look for it? Solaris often requires hacking with LD_RUN_PATH or some such to deal with nonstandard installation locations for shared libraries. regards, tom lane CONFIDENTIALITY WARNING This communication, including any attachments, is for the exclusive use of addressee and may contain proprietary and/or confidentialinformation. If you are not the intended recipient, any use, copying, disclosure, dissemination or distributionis strictly prohibited. If you are not the intended recipient, please notify the sender immediately by returne-mail, delete this communication and destroy all copies. AVERTISSEMENT RELATIF À LA CONFIDENTIALITÉ Ce message, ainsi que les pièces qui y sont jointes, est destiné à l’usage exclusif de la personne à laquelle il s’adresseet peut contenir de l’information personnelle ou confidentielle. Si le lecteur de ce message n’en est pas le destinataire,nous l’avisons par la présente que toute diffusion, distribution, reproduction ou utilisation de son contenuest strictement interdite. Veuillez avertir sur-le-champ l’expéditeur par retour de courrier électronique et supprimezce message ainsi que toutes les pièces jointes.
В списке pgsql-bugs по дате отправления: