From: | owen hartnett <owen(at)clipboardinc(dot)com> |
---|---|
To: | "Leif B(dot) Kristensen" <leif(at)solumslekt(dot)org> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Strange Postgresql behavior solved |
Date: | 2008-07-26 17:41:04 |
Message-ID: | 709F663C-C621-493E-844B-7C313C71573B@clipboardinc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jul 26, 2008, at 2:32 AM, "Leif B. Kristensen"
<leif(at)solumslekt(dot)org> wrote:
> On Saturday 26. July 2008, Owen Hartnett wrote:
>> Probably some funky stuff with the router (not one of their expensive
>> ones) that caused all the consternation, but I originally thought
>> corrupt database (because I could get 117 records to come out fine,
>> but not the 118th). Also, I had narrowed it down to failing only
>> when accessing the last three fields of that 118th record, the first
>> 40 fields were fine.
>
> That sounds a lot like the "game mode" router bug:
>
> http://www.azureuswiki.com/index.php/Torrents_stop_at_99_percent
Yes. It looks like just the behavior. The read failed in the exact
same record every time, even at the same column, and the server is
sitting in a DMZ.
-Owen
From | Date | Subject | |
---|---|---|---|
Next Message | Yi Zhao | 2008-07-26 19:12:18 | how to remove the duplicate elements from an array? |
Previous Message | Steve Atkins | 2008-07-26 17:10:55 | Wrapper to use correct version of psql? |