From: | lec <limec(at)streamyx(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Scott Marlowe <smarlowe(at)qwest(dot)net>, Alvaro Herrera Munoz <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Losing records when server hang |
Date: | 2004-08-09 15:13:21 |
Message-ID: | 41179491.8010004@streamyx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
>"Scott Marlowe" <smarlowe(at)qwest(dot)net> writes:
>
>
>>On Sun, 2004-08-08 at 21:26, Alvaro Herrera Munoz wrote:
>>
>>
>>>If this is only one backend, then I'd love to see how did he do that.
>>>
>>>
>
>
>
>>Me too :-)
>>
>>
>
>Given a disk drive that lies about write complete (which is to to say,
>most consumer-grade IDE gear), it's at least theoretically possible.
>But it doesn't sound real likely, especially if the machine didn't
>actually lose power.
>
>
It's a SCSI, RAID-5 on a Dell server.
>I was wondering what he meant by "hang", as well as what he meant by
>"commit". The overall lack of detail in the report is notable.
>
>
The hardware actually "hang". The Dell engineers came and replaced the
motherboard but couldn't tell what the actual fault was.
Commit as in 'COMMIT'. 'Records' 1,2,3,4,5,6,7,8,9,10 are actually
transactions. I'm as puzzled as to why I lost the transactions in the
middle but got the last transaction.
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | lec | 2004-08-09 15:15:56 | Re: Losing records when server hang |
Previous Message | lec | 2004-08-09 15:07:34 | Re: Losing records when server hang |