| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Justin Clift <justin(at)postgresql(dot)org>, 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 01:05:48 |
| Message-ID: | 200201250105.g0P15mc22559@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> 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.
We added some PostgreSQL code to touch the socket file during
checkpoints, and I thought that was in 7.1.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-01-25 01:12:15 | Re: PostgreSQL crashes with Qmail-SQL |
| Previous Message | Tom Lane | 2002-01-25 00:51:05 | Re: PostgreSQL crashes with Qmail-SQL |