pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feed/tmp/.s.PGSQL.${PGPORT}
2+ messages / 2 participants
[nested] [flat]
* /tmp/.s.PGSQL.${PGPORT}
@ 2000-08-18 14:58 Jim O'Rourke <JimO@Routescape.com>
2000-08-19 05:35 ` Re: /tmp/.s.PGSQL.${PGPORT} Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 2+ messages in thread
From: Jim O'Rourke @ 2000-08-18 14:58 UTC (permalink / raw)
To: pgsql-interfaces
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.
The only workaround I’ve come up with is to kill and restart the postmaster
when a connection attempt fails. This works fine except when the admin
wants the server down, ie: maintenance.
Any other suggestions would be appreciated !!
Thanks
Jim O’Rourke
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: /tmp/.s.PGSQL.${PGPORT}
2000-08-18 14:58 /tmp/.s.PGSQL.${PGPORT} Jim O'Rourke <JimO@Routescape.com>
@ 2000-08-19 05:35 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2000-08-19 05:35 UTC (permalink / raw)
To: Jim O'Rourke <JimO@Routescape.com>; +Cc: pgsql-interfaces
"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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2000-08-19 05:35 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-08-18 14:58 /tmp/.s.PGSQL.${PGPORT} Jim O'Rourke <JimO@Routescape.com>
2000-08-19 05:35 ` Tom Lane <tgl@sss.pgh.pa.us>
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