Connecting using an existing socket (libpq).

From: jbi130(at)yahoo(dot)com
To: pgsql-general(at)postgresql(dot)org
Subject: Connecting using an existing socket (libpq).
Date: 2004-01-12 18:05:49
Message-ID: 87fzelnimh.fsf@syn.codemonkey.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I have a 3 tier client/server application where the client connection
to the server which then uses PostgreSQL. I'd like to extend the
client to have direct access to PostgreSQL but do not want to open up
postgresql to the internet.

So, I'd like to tunnel the libpq connection over the existing secure
socket. My preferred solution would be for the client to pass libpq
an already connected file descriptor (so I can prevent binding a port
to localhost).

Is such a thing possible without hacking libpq? Are there other
options I should be looking at that don't involve PostgreSQL listening
on the evil internet?

Thanks.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message D. Dante Lorenso 2004-01-12 18:42:10 Dump/Restore ordering problem?
Previous Message elein 2004-01-12 18:01:49 Re: History-based (or logged) database.