We're trying to avoid creating any unnecessary files, especially outside
of the product installation tree. Look at this as a policy.
Experience shows that sooner or later some of your customers ask you:
what is this /tmp/.s.PGSQL.xxx file is? What do I need it for?
Also some admins known to periodically clean out /tmp, /var/run, etc.
Mike.
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> Sent: Thursday, February 13, 2003 8:38 PM
> To: michael@synchronicity.com
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Do we always need the socket file?
>
>
> 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@candle.pha.pa.us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square,
> Pennsylvania 19073
>
