BUG #5820: FATAL: could not access file "libpqwalreceiver": No such file or directory

Started by Leif Gunnar Erlandsenover 15 years ago3 messagesbugs
Jump to latest

The following bug has been logged online:

Bug reference: 5820
Logged by: Leif Gunnar Erlandsen
Email address: leif@lako.no
PostgreSQL version: 9.0.2
Operating system: RedHat Enterprise 5.4 64 bit
Description: FATAL: could not access file "libpqwalreceiver": No
such file or directory
Details:

Postgresql compiled from source and placed in
/local/postgresql/9.0.2

libpqwalreceiver.so is located in /local/postgresql/9.0.2/lib64 while
recovery is trying to load it from /local/postgresql/9.0.2/lib

With symlink to libpqwalreceiver.so in lib problem disappears.

Regards
Leif Gunnar Erlandsen

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Leif Gunnar Erlandsen (#1)
Re: BUG #5820: FATAL: could not access file "libpqwalreceiver": No such file or directory

"Leif Gunnar Erlandsen" <leif@lako.no> writes:

Postgresql compiled from source and placed in
/local/postgresql/9.0.2

libpqwalreceiver.so is located in /local/postgresql/9.0.2/lib64 while
recovery is trying to load it from /local/postgresql/9.0.2/lib

.../lib is where I'd expect it to be. Did you move the libraries to
.../lib64 by hand, or something like that? If so, you would need to
modify the paths chosen by configure; you can't just manually
rearrange the installation tree.

regards, tom lane

In reply to: Tom Lane (#2)
Re: BUG #5820: FATAL: could not access file "libpqwalreceiver": No such file or directory

Tom Lane <tgl@sss.pgh.pa.us> wrote:

"Leif Gunnar Erlandsen" <leif@lako.no> writes:

Postgresql compiled from source and placed in
/local/postgresql/9.0.2

libpqwalreceiver.so is located in /local/postgresql/9.0.2/lib64 while
recovery is trying to load it from /local/postgresql/9.0.2/lib

.../lib is where I'd expect it to be. Did you move the libraries to
.../lib64 by hand, or something like that? If so, you would need to
modify the paths chosen by configure; you can't just manually
rearrange the installation tree.

regards, tom lane

This IS not a bug.
As Tom Lane said, the libraries was moved by a script called "install_fixup" in
our central build routine.

regards
Leif Gunnar Erlandsen