From: | Giles Lean <giles(at)nemeton(dot)com(dot)au> |
---|---|
To: | sk9887(at)sbc(dot)com, benk(at)aiinet(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #882: Cannot manually log in to database. |
Date: | 2003-01-24 14:02:54 |
Message-ID: | 1162.1043416974@nemeton.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
[ Where *did* that Reply-To: line come from -- it's broken ...
repl: bad addresses:
benk(at)aiinet(dot)com; -- extraneous semi-colon
]
> 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.
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);
If you can't write that into C, drop me a line, and I'll send you the
code. Most touch(1) implementations would also do the right thing, so
you could try that too. Then put whatever solution you choose into
cron, and you're done.
Regards,
Giles
From | Date | Subject | |
---|---|---|---|
Next Message | Wolfgang Walter | 2003-01-24 14:03:07 | pgtcl combined with view with certain insert/update-rules => crash |
Previous Message | Rod Taylor | 2003-01-24 12:45:08 | Re: Bug #880: COMMENT ON DATABASE depends on current |