| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | benk(at)aiinet(dot)com, sk9887(at)sbc(dot)com, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Bug #882: Cannot manually log in to database. |
| Date: | 2003-01-23 20:48:44 |
| Message-ID: | 28043.1043354924@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
pgsql-bugs(at)postgresql(dot)org writes:
> okapview# /opt/pgsql-7.1.3/bin/psql -U postgres -d AppliedView
> psql: connectDBStart() -- connect() failed: No such file or directory
> Is the postmaster running locally
> and accepting connections on Unix socket '/tmp/.s.PGSQL.5432'?
> Stopping and starting the postmaster daemon clears up this problem, but this problem creeps up about 2 times a week, and is a major annoyance.
Sounds to me like you've got a cron script that removes everything in
tmp about twice a week. I suggest teaching it not to remove socket
files. On most Unixen the mod date on a socket file isn't changed by
normal activity, so a tmp-cleaner that only pays attention to the mod
date will mistakenly decide a socket is fair game for removal.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-01-23 21:29:47 | Re: Postgres 7.3 in PPC |
| Previous Message | pgsql-bugs | 2003-01-23 18:06:07 | Bug #882: Cannot manually log in to database. |