| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Justin Clift <justin(at)postgresql(dot)org> |
| Cc: | Michael Devogelaere <michael(at)digibel(dot)be>, Jan Wieck <janwieck(at)yahoo(dot)com>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL crashes with Qmail-SQL |
| Date: | 2002-01-25 00:51:05 |
| Message-ID: | 21436.1011919865@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Justin Clift <justin(at)postgresql(dot)org> writes:
>> No such file?? Hard to believe that that could happen while the
>> postmaster was still running. Unless something else had decided to
>> delete the socket file from /tmp. The postmaster certainly would not
>> do it.
> This provides an interesting lead. There's at least one linux
> distribution which does this. Part of the cron'd maintenance scripts
> delete all the files in /tmp, and therefore play havoc....
Yeah, I do recall that some versions had a tmp-scrubber that didn't make
any exception for socket files. But it's kind of a big coincidence to
assume that would happen just while Michael was running his benchmark.
Not sure I credit it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-01-25 01:05:48 | Re: PostgreSQL crashes with Qmail-SQL |
| Previous Message | Marc G. Fournier | 2002-01-25 00:35:12 | Re: Ready for RC2 I guess... |