Re: TCP/IP Sockets, UNIX Sockets

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Daniel Åkerud <zilch(at)home(dot)se>
Cc: PostgreSQL-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: TCP/IP Sockets, UNIX Sockets
Date: 2001-06-22 20:03:47
Message-ID: Pine.LNX.4.30.0106222200271.727-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Daniel Åkerud writes:

> How do you force pgsql to use either TCP/IP Sockets or UNIX Sockets?

This depends greatly on what exactly "pgsql" stands for. In the server
you can turn off the TCP/IP socket, so no client can use it. In the
client library you just connect() to whatever socket you want. The
existing clients should have a function or an option to decide. For
example in psql you use -h 'hostname' for TCP/IP, or -h '' for unix
domain.

> And how do you know which one it uses?

You follow the documentation of the interface you use and trust it's doing
the right thing. When in doubt use netstat or something similar.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-06-22 20:09:53 Re: Multiple Indexing, performance impact
Previous Message Thomas T. Thai 2001-06-22 19:48:49 select to combine 2 tables