[BUGS] Getting "getsockopt(TCP_KEEPALIVE) failed" LOG message in PG Logs on Solaris 10
Hi, I am getting "getsockopt(TCP_KEEPALIVE) failed: Option not supported by protocol" log message in the PG Logs whenever I run a query referencing "pg_catalog.pg_settings" on Solaris 10 (both Sprac and x86-64). You can reproduce this case by running a query like: SELECT name, setting, unit FROM pg_catalog.pg_settings; This happens only the first time you execute the query though. This issue was reproducible to me on both PostgreSQL 9.0.4 and PostgreSQL 9.2.4. This happens when I run the query via psql or pgAdminIII by connecting to the database server over the TCP socket (i.e. by providing host details in -h). Same behavior is not reproducible if I connect to database server over Unix Socket. I am not sure if this has been reported before, but I thought I should bring this issue to your notice. regards, *Dhiraj Chawla* Senior Software Engineer EnterpriseDB Corporation The Enterprise PostgreSQL Company Phone: +91-20-30589522
[BUGS] BUG #8513: Error recognizing data type in union
The following bug has been logged on the website: Bug reference: 8513 Logged by: Tommi Korhonen Email address: tommi.korho...@thl.fi PostgreSQL version: 8.4.17 Operating system: Redhat Linux Description: Example: create table t1(a integer); create table t2(b integer); create table t3(c integer); select null from t1 union all select null from t2 union all select c from t3; produces an error ERROR: UNION types text and integer cannot be matched LINE 5: select c from t3; but select null from t2 union all select c from t3; works correctly. So it seems that if there are more than one nulls before field c in union PostreSQL thinks merged field's data type is text. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #8500: Upgrade to postgis 2.1 breaks existing databases
Hi, I *think* I fixed this problem. We will release updated packages tomorrow, along with the PostgreSQL minor release updates. Please let me know if they still don't work. :) Regards, Devrim On Fri, 2013-10-04 at 13:26 +, kyri...@alumni.princeton.edu wrote: > The following bug has been logged on the website: > > Bug reference: 8500 > Logged by: Kriton Kyrimis > Email address: kyri...@alumni.princeton.edu > PostgreSQL version: 9.2.4 > Operating system: Scientific Linux 6.4 > Description: > > The version of postgis, available in the postgresql yum repository for > postgis 9.2, was recently upgraded to version 2.1. This breaks existing > databases built with postgis 2.0, as queries involving postgis fail with the > error message "ERROR: could not access file "$libdir/postgis-2.0": No such > file or directory" > > > This includes backing up the databases, so upgrading them to use postgis 2.1 > may not even be an option, if a hard upgrade is required. > > > I have downgraded all postgis2_92 packages to version 2.0.4 and excluded > them from future upgrades, but I'd recommend reverting to that version in > the repositories, as well. At the very least, please ensure that version > 2.0.x of the packages remains available in the future. Better still, provide > alternative postgis21_92-* packages, for those wishing to use the latest > version, without affecting those that use the previous version. > > > -- Devrim GÜNDÜZ Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz signature.asc Description: This is a digitally signed message part
[BUGS] BUG #8514: cache lookup failed for relation 421062806
The following bug has been logged on the website: Bug reference: 8514 Logged by: Tejas Email address: shahtejas2...@gmail.com PostgreSQL version: 8.4.0 Operating system: Linux 7.2 Description: my postgresql running file . but sometime i found cache lookup failed for relation 421062806 error in postgresql log. can anyone tell me significant of this error. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #8515: Random 'relation "..." does not exist'
The following bug has been logged on the website: Bug reference: 8515 Logged by: Nicolas Buduroi Email address: nbudu...@gmail.com PostgreSQL version: 9.2.4 Operating system: ArchLinux Description: We've recently migrated an application from MySQL to Postgres and I've been experiencing some really strange and random bugs. The application is a pretty simple Rails application and the Postgres setup is the default one provided by ArchLinux. Basically, at some point a query, update or insert will not work and complain about a table not existing, but that table was used without any issue previously. Closing the running connection to the database and reconnecting make that error disappear. Two concurrent connections (one from a console and another from the app) could be contradicting themselves, one giving the error and the other not. This only happen on a development machine which is running version 9.2.4 of Postgres. We've not encountered this error on our production/staging/ci servers which are running Postgres 9.1.9 version. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
