From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Radoslaw Zielinski <radek(at)pld-linux(dot)org> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: 8.4.0 data loss / HOT-related bug |
Date: | 2009-08-21 16:55:44 |
Message-ID: | 407d949e0908210955n7deb2946p3257ab21e30e0054@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
2009/8/21 Radoslaw Zielinski <radek(at)pld-linux(dot)org>:
> Greg Stark <gsstark(at)mit(dot)edu> [2009-08-21 18:03]:
>> On Fri, Aug 21, 2009 at 4:04 PM, Radoslaw Zielinski<radek(at)pld-linux(dot)org> wrote:
>>> This particular row currently has last_modified="2009-08-11", but table_log
>>> says it has been updated on "2009-08-12" -- so, data loss.
>
>> These are all very low transaction ids. you say it was a week of
>> production before this happened?
>
> Upgraded around:
> $ rpm -q postgresql --qf '%{INSTALLTIME}' | xargs perl -le 'print~~localtime shift'
> Fri Aug 7 10:06:44 2009
Is this, perchance, new hardware? Did you test the memory in it?
Do you have other records that have "disappeared"?
From | Date | Subject | |
---|---|---|---|
Next Message | Radoslaw Zielinski | 2009-08-21 17:38:00 | Re: 8.4.0 data loss / HOT-related bug |
Previous Message | Pavel Stehule | 2009-08-21 16:52:06 | Re: BUG #5001: can not prepare for where Re: BUG #5001: can not prepare for where $1 is null is null |