exposing conn->sock? - Mailing list pgsql-interfaces

From Alex Pilosov
Subject exposing conn->sock?
Date
Msg-id Pine.BSO.4.10.10105291955120.28420-100000@spider.pilosoft.com
Whole thread Raw
Responses Re: exposing conn->sock?
List pgsql-interfaces
Hi,

I have a question whether a patch which would expose conn->sock (the
actual socket connected to the server) via a function would be
acceptable/accepted. My application does essentially a select() loop on
various sockets, and is also waiting for asynchronous notifications from
database. While I know about pqWait, pqReadReady etc, these all require
busy-waiting of some sort and do not allow for immediate notification when
combined with waiting on some other fds.

So, is there some particular reason conn->sock is not exposed?

-alex



pgsql-interfaces by date:

Previous
From: Joel Burton
Date:
Subject: Re: gar ...weird odbc thing
Next
From: Tom Lane
Date:
Subject: Re: exposing conn->sock?