I did install successully postgres 8.03 but I am getting the following
error message in the syslog eventhough /var/pgsql/data is pointing to new
configuration file which is postgres 8.03.
"ksqo" is configuration parameter for the postgres 7.4
Please advice me to fix this problem.
Jun 20 18:38:41 lab5md9181 postgres[2552]: [2-1] 2005-06-20 18:38:41 EDT
ERROR:
unrecognized configuration parameter "ksqo"
Jun 20 18:38:41 lab5md9181 postgres[2553]: [2-1] 2005-06-20 18:38:41 EDT
ERROR:
unrecognized configuration parameter "ksqo"
Jun 20 18:38:41 lab5md9181 postgres[2554]: [2-1] 2005-06-20 18:38:41 EDT
ERROR:
unrecognized configuration parameter "ksqo"
Thanks
Prasad
----- Original Message -----
From: "Devrim GUNDUZ" <[EMAIL PROTECTED]>
To: "Prasad Duggineni" <[EMAIL PROTECTED]>
Cc: <pgsql-general@postgresql.org>
Sent: Wednesday, June 15, 2005 11:11 AM
Subject: Re: [GENERAL] 8.03 postgres install error
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Wed, 15 Jun 2005, Prasad Duggineni wrote:
I am getting the following error when i try to install the postgres 8.03
. It seems to be problem with the installing postgres libs. Plesae advice
me to fix this problem.
warning: postgresql-libs-8.0.3-1PGDG.i686.rpm: V3 DSA signature: NOKEY,
key ID 748f7d0e
error: Failed dependencies:
libecpg.so.4 is needed by postgresql-libs-8.0.3-1PGDG
libpgtypes.so.1 is needed by postgresql-libs-8.0.3-1PGDG
libpq.so.3 is needed by postgresql-libs-8.0.3-1PGDG
Suggested resolutions:
postgresql-libs-7.3.2-3.i386.rpm
http://developer.PostgreSQL.org/~devrim/compat-postgresql-libs-3-3PGDG.i686.rpm
is the RPM you need.
Regards,
- --
Devrim GUNDUZ
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.tdmsoft.com.tr http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFCsEUotl86P3SPfQ4RAtbeAJ9zMDpaLNpKUDkezoisLiEKUdCNoQCgrZ0s
rIfdpnpG5tBjg5gUu85MoiI=
=AvjU
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
