pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedexposing conn->sock?
2+ messages / 2 participants
[nested] [flat]
* exposing conn->sock?
@ 2001-05-30 00:05 Alex Pilosov <alex@pilosoft.com>
0 siblings, 1 reply; 2+ messages in thread
From: Alex Pilosov @ 2001-05-30 00:05 UTC (permalink / raw)
To: 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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: exposing conn->sock?
@ 2001-05-30 04:09 Tom Lane <tgl@sss.pgh.pa.us>
parent: Alex Pilosov <alex@pilosoft.com>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2001-05-30 04:09 UTC (permalink / raw)
To: Alex Pilosov <alex@pilosoft.com>; +Cc: pgsql-interfaces
Alex Pilosov <alex@pilosoft.com> writes:
> So, is there some particular reason conn->sock is not exposed?
Apparently you didn't notice PQsocket() yet ...
regards, tom lane
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2001-05-30 04:09 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-05-30 00:05 exposing conn->sock? Alex Pilosov <alex@pilosoft.com>
2001-05-30 04:09 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox