From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim O'Rourke <JimO@Routescape.com>
Cc: 'pgsql-interfaces@postgresql.org' <pgsql-interfaces@postgresql.org>
Subject: Re: /tmp/.s.PGSQL.${PGPORT}
Date: Sat, 19 Aug 2000 01:35:47 -0400
Message-ID: <22269.966663347@sss.pgh.pa.us> (raw)
In-Reply-To: <614E0D291FEAD311BD370050DA76B9D0041A2A@EXCHSERV>
References: <614E0D291FEAD311BD370050DA76B9D0041A2A@EXCHSERV>
"Jim O'Rourke" <JimO@Routescape.com> writes:
> Is anybody else having problems with the /tmp/.s.PGSQL.${PGPORT} file being
> removed by “cleantmp” et al.
> /tmp is a dumping ground that rightly gets cleaned out periodically.
/tmp is a damfool place to have put the socket file, no doubt about that.
But we are stuck with it now if we don't want to break existing
applications --- the location of the socket file is a critical hardwired
part of the wire-level protocol, since the client and server MUST both
know it *before* any communication happens.
This was argued back around 6.4, IIRC, and we decided to do nothing.
The argument in favor of doing nothing seems even stronger now, with a
couple more years worth of existing clients out there...
Solutions:
1. Tweak your tmp-cleaning cron job to not remove the socket file.
2. Use IP instead of Unix-socket connections, so that your clients
don't care whether the socket file is there or not.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, JimO@Routescape.com
Subject: Re: /tmp/.s.PGSQL.${PGPORT}
In-Reply-To: <22269.966663347@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox