Re: Error - could not get socket error status: Invalid argument

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jayaraman, Rajaram (STSD)" <rajaram(dot)j(at)hp(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Error - could not get socket error status: Invalid argument
Date: 2009-12-07 15:12:47
Message-ID: 4113.1260198767@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Jayaraman, Rajaram (STSD)" <rajaram(dot)j(at)hp(dot)com> writes:
> I am using postgres 8.4.0 version and have compiled 64bit libpq library.

How did you do that exactly?

> While conneting I am getting error
> " could not get socket error status: Invalid argument"

A bit of grepping shows that it failed here:

ACCEPT_TYPE_ARG3 optlen = sizeof(optval);

if (getsockopt(conn->sock, SOL_SOCKET, SO_ERROR,
(char *) &optval, &optlen) == -1)
{
appendPQExpBuffer(&conn->errorMessage,
libpq_gettext("could not get socket error status: %s\n"),
SOCK_STRERROR(SOCK_ERRNO, sebuf, sizeof(sebuf)));

The most likely bet seems to be that optlen isn't of the width the
kernel is expecting, which would imply that configure didn't choose
the type ACCEPT_TYPE_ARG3 correctly, which would imply that HP's
done something weird and unlike every other platform. Which would
not be too much of a surprise :-(. Or possibly you gave configure
some inconsistent arguments that confused it.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rob W 2009-12-07 15:33:16 Query using partitioned table hangs
Previous Message Merlin Moncure 2009-12-07 15:08:39 Re: Array comparison & prefix search