| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | David Parker <dparker(at)tazznetworks(dot)com> |
| Cc: | postgres general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: client interfaces |
| Date: | 2005-04-12 20:10:29 |
| Message-ID: | 20050412201029.GA29388@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Apr 12, 2005 at 10:51:09 -0400,
David Parker <dparker(at)tazznetworks(dot)com> wrote:
> Is there anything like a client library for postgres that does not use
> tcp/ip as the protocol? As part of the performance tuning of our
> application, the question was posed to me whether there was a more
> "direct" sort of API that would not require going through the tcp/ip
> stack. I assume the answer to this is "no", and I see no hint of
> anything in the source code, but I thought I would ask the question,
> just to be sure.
You can use domain sockets when on the same host as the server.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-04-12 20:48:53 | Re: Composite type versus Domain constraints. |
| Previous Message | James Robinson | 2005-04-12 20:07:12 | Composite type versus Domain constraints. |