From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alex Pilosov <alex@pilosoft.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: exposing conn->sock?
Date: Wed, 30 May 2001 00:09:23 -0400
Message-ID: <20760.991195763@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.BSO.4.10.10105291955120.28420-100000@spider.pilosoft.com>
References: <Pine.BSO.4.10.10105291955120.28420-100000@spider.pilosoft.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, alex@pilosoft.com
Subject: Re: exposing conn->sock?
In-Reply-To: <20760.991195763@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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