| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Yann Ramin <atrus(at)atrustrivalie(dot)org> |
| Cc: | "Justin S(dot)" <cometfly(at)cometfly(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Address already in use? |
| Date: | 2001-04-14 01:32:07 |
| Message-ID: | 9297.987211927@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Yann Ramin <atrus(at)atrustrivalie(dot)org> writes:
> Simply remove /tmp/.s.PGSQL.5432. Its safe to do this in a startup script.
> Postgres isn't too good about removing its UNIX socket if it has a
> semi-nonclean shutdown (system reboot among other things).
Although that's been a standard workaround for a long time, I've always
considered it fairly dangerous: what if the script is invoked at a time
other than system boot? Fortunately, it should no longer be necessary
as of Postgres 7.1 --- we now have code to check for and remove a
leftover socket file safely. I now recommend removing any automatic
socket-file deletion you may have in your startup script.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-04-14 01:37:03 | Re: local security |
| Previous Message | Mitch Vincent | 2001-04-14 01:28:15 | Re: anti Christian bias? |