>> Philip's cases are valuable tests, but not typical usage... With
>> reasonable settings, chills will happen only during loads and mass
>> inserts. The chances of modifying or deleting a record that's been
>> chilled are small, and the chances of having a multi-level modify /
>> chill / delete cycle are lower still.
Please find below an email from Kevin on another thread that describes a
potential chill/thaw/backlogging scenario that is not a load or a mass
insert -- attempting to generate a report by making multiple passes through
the entire data while writing intermediate values in a summary table. If you
decide to mark the start of your execution by inserting a timestamp in some
log table, your transaction has become an update one and thus the serial log
will grow and the memory will fill up with old record versions.
Philip Stoev
----- Original Message -----
From: "Kevin Lewis" <Kevin.Lewis@stripped>
To: "Ingo Strüwing" <Ingo.Struewing@stripped>
Cc: "Øystein Grøvlen" <Oystein.Grovlen@stripped>; "'dev-backup'"
<dev-backup@stripped>; <falcon-private@stripped>
Sent: Wednesday, October 29, 2008 9:28 PM
Subject: Re: Restore makes ongoing transactions see empty tables
> A single transaction may make a couple passes through a table summing up
> certain columns for certain criteria. We do not want that data to change
> in the middle of that transaction, for example, between pass one and pass
> two. Currently, a table will be truncated and then the restored data will
> get replaced within a new transaction. The truncate will be seen
> immediately by the existing transaction, but the restored data, being
> transactional, will not be seen.
