Re: Bug #882: Cannot manually log in to database.
От | Tom Lane |
---|---|
Тема | Re: Bug #882: Cannot manually log in to database. |
Дата | |
Msg-id | 13541.1043424228@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Bug #882: Cannot manually log in to database. (Giles Lean <giles@nemeton.com.au>) |
Ответы |
Re: Bug #882: Cannot manually log in to database.
|
Список | pgsql-bugs |
Giles Lean <giles@nemeton.com.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
В списке pgsql-bugs по дате отправления: