BUG #7859: postgresql92-libs fails to create ld.so.conf.d symlink

[h***@oakland.edu]

The following bug has been logged on the website:

Bug reference: 7859
Logged by: Tomas Hajek
Email address: ***@oakland.edu
PostgreSQL version: 9.2.3
Operating system: Red Hat Enterprise Linux Server release 6.3
Description:

1. Fresh install of RHEL 6.3 x86_64
2. yum update
3. postgresql repo with:
wget
http://yum.postgresql.org/9.2/redhat/rhel-6-x86_64/pgdg-redhat92-9.2-7.noarch.rpm
sudo yum install pgdg-redhat92-9.2-7.noarch.rpm

4. yum install postgresql92-server postgresql92-libs postgresql92-contrib
postgresql92

5. Initialize the database with:
sudo -u postgres -H /usr/pgsql-9.2/bin/initdb -D /var/lib/pgsql/9.2/data

6. #Start the database server
sudo service postgresql-9.2 start

7. sudo -u postgres -H psql
results in "psql: error while loading shared libraries: libpq.so.5: cannot
open shared object file: No such file or directory"

8. Checking /etc/ld.so.conf.d shows that no postgresql-pgdg-libs.conf
symlink present.

Similar procedure worked a week ago against 9.2.2.

I assume this is similar in nature to bug #7857.

[Devrim GÜNDÜZ]

Hi,

Thanks for the report. Fixed in 9.2.3-2. Packages just hit repository.

Regards, Devrim

Post by h***@oakland.edu
Bug reference: 7859
Logged by: Tomas Hajek
PostgreSQL version: 9.2.3
Operating system: Red Hat Enterprise Linux Server release 6.3
1. Fresh install of RHEL 6.3 x86_64
2. yum update
wget
http://yum.postgresql.org/9.2/redhat/rhel-6-x86_64/pgdg-redhat92-9.2-7.noarch.rpm
sudo yum install pgdg-redhat92-9.2-7.noarch.rpm
4. yum install postgresql92-server postgresql92-libs postgresql92-contrib
postgresql92
sudo -u postgres -H /usr/pgsql-9.2/bin/initdb -D /var/lib/pgsql/9.2/data
6. #Start the database server
sudo service postgresql-9.2 start
7. sudo -u postgres -H psql
results in "psql: error while loading shared libraries: libpq.so.5: cannot
open shared object file: No such file or directory"
8. Checking /etc/ld.so.conf.d shows that no postgresql-pgdg-libs.conf
symlink present.
Similar procedure worked a week ago against 9.2.2.
I assume this is similar in nature to bug #7857.