Re: 8.4.0 data loss / HOT-related bug

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

The first mention of the error in the app's output:
[info] *** Request 5532 (0.008/s) [7283] [Wed Aug 19 13:06:35 2009] ***

User has reported "disappearing rows" at 12 Aug 2009, 16:58.

> How did you migrate your data? Was it a normal pg_dump restore? Or did
> you do anything funny with slony or pg_migrate?

Plain regular dump/restore (from text dump). There's no slony or
anything on this database except for table_log and the trigger to update
last_modified.

In case it might be relevant: locale C, encoding utf8.

--
Radosław Zieliński <radek(at)pld-linux(dot)org>