| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | michael(at)synchronicity(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Do we always need the socket file? |
| Date: | 2003-02-14 01:38:07 |
| Message-ID: | 200302140138.h1E1c7h07982@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Brusser wrote:
> I have Postgres 7.2.1 configured to listen on TCP/IP port.
> When the server starts up it still creates the socket file in /tmp.
> Removing this file manually does not seem to cause any problem for the
> application.
>
> Is there a way to prevent postmaster from creating this file?
> Is this really safe to remove the socket file, or would it create
> some problem that I won't necessarily see?
I guess the big question is why you don't want the file created? If you
have 'local' disabled in pg_hba.conf, it doesn't allow connections.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2003-02-14 01:39:13 | Re: location of the configuration files |
| Previous Message | Tom Lane | 2003-02-14 01:29:52 | Re: Someone's broken psql's connection-failure error reporting |