From: | Dhiraj Chawla <dhiraj(dot)chawla(at)enterprisedb(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Getting "getsockopt(TCP_KEEPALIVE) failed" LOG message in PG Logs on Solaris 10 |
Date: | 2013-10-09 07:29:03 |
Message-ID: | CAJgtxT6QL0_Gt+TkSDw=q1=YVJkT73FoSrtStcu5Hy+-SXn8rw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | tommi.korhonen | 2013-10-09 12:39:58 | BUG #8513: Error recognizing data type in union |
Previous Message | Mátyás Milos | 2013-10-08 21:57:23 | win8 |
From | Date | Subject | |
---|---|---|---|
Next Message | Jesse Long | 2013-10-09 07:50:03 | Incorrect index being used |
Previous Message | Bob Futrelle | 2013-10-09 04:27:20 |