From: | "Eric B(dot) Ridge" <ebr(at)tcdi(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org, Joey Adams <jea(at)tcdi(dot)com> |
Subject: | Re: Possible data corruption with Postgres 7.4.8 |
Date: | 2006-03-14 05:10:49 |
Message-ID: | E41F30CB-CEFD-42F3-8D01-AAF39D8B9503@tcdi.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mar 13, 2006, at 11:12 PM, Tom Lane wrote:
> The relation-extension race condition could explain recently-added
> tuples simply disappearing, though if it happened in more than one
> table
> you'd have to assume that the race condition window got hit more than
> once. The slru race condition is even narrower, but if it hit then it
> could cause tuples inserted by the same transaction into different
> tables to become lost. Either of these seem to match your symptoms?
If "tuples inserted" can mean "tuples inserted by means of an UPDATE
statement", then I think the latter applies.
In digging further, the record which disappeared should have had
corresponding records in three other tables, each of which were also
missing. The update across all four tables would have been part of
the same transaction (they're updated at the same time as part of an
ON UPDATE RULE against a VIEW).
eric
From | Date | Subject | |
---|---|---|---|
Next Message | Nick Johnson | 2006-03-14 06:45:47 | Dynamic function execution? |
Previous Message | Tom Lane | 2006-03-14 04:12:55 | Re: Possible data corruption with Postgres 7.4.8 |