From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Giles Lean <giles(at)nemeton(dot)com(dot)au> |
Cc: | sk9887(at)sbc(dot)com, benk(at)aiinet(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #882: Cannot manually log in to database. |
Date: | 2003-01-24 16:03:48 |
Message-ID: | 13541.1043424228@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Giles Lean <giles(at)nemeton(dot)com(dot)au> writes:
> Either teach your /tmp cleaner not to clean out the socket files as
> Tom Lane suggested, or arrange to update the socket timestamps. I
> think it's easier to just keep updating the timestamps -- then I don't
> have to educate each new system administrator.
> utimes("/tmp/.s.PGSQL.5432", (const struct timeval *) 0);
Hm, do you think that's portable?
There is already code in the postmaster to touch the socket lock file
every few minutes, so as to keep tmp-cleaners from zapping it. (Or at
least there once was; I can't find it right now.) If we could do the
same for the socket file it'd be really nice. But I didn't think there
was any portable way to update the mod timestamp on a socket.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kinsey, Ben | 2003-01-24 16:14:23 | Re: Bug #882: Cannot manually log in to database. |
Previous Message | Wolfgang Walter | 2003-01-24 14:03:07 | pgtcl combined with view with certain insert/update-rules => crash |