From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Wierd panic with 7.4.7 |
Date: | 2005-06-28 18:04:29 |
Message-ID: | 22290.1119981869@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>> Do you know what the dead client was doing?
> Unfortunately I don't. We didn't have PID logging turned on so I can't
> tell which process it was. The only thing I was told was,
> "I am running a Full Vacuum, CRAP the server just died ;)"
Hmm ... VACUUM FULL is a tad weird because it marks itself committed
before it does the last stage of the operation (ie truncating the
relation). I suppose it is possible that an error during that last
stage would have this symptom. There's still the question of why
the postmaster log doesn't show the hypothetical initial error, though.
(Also, it's likely that there's some defense against this scenario in
VACUUM FULL, otherwise we'd hear this kind of report more often, I
should think. I don't have time to go looking right now though.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-28 18:11:05 | Re: CVS tip build failure (win32) |
Previous Message | Tom Lane | 2005-06-28 17:58:01 | Re: Occupied port warning |