Re: CREATE TABLE, load and freezing

["Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>]

On Fri, Feb 29, 2008 at 9:15 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>
>  We've heard that idea before, and it's just as bad as it was when
>  proposed before.  "Pre-frozen" tuples eliminate any possibility of
>  tracking when a tuple was inserted; which is extremely important to know
>  when you are trying to do forensic analysis of a broken table.  The
>  point of the current design is to not throw away information about tuple
>  insertion time until the tuple is old enough that the info is (probably)
>  not interesting anymore.
>

Understood. But if we consider a special case of creation and loading
of a table in a single transaction, we can possibly save the information
that the table was loaded with pre-frozen tuples with xmin equals to the
transaction creating the table.

 Thanks,
Pavan


-- 
Pavan Deolasee
EnterpriseDB     http://www.enterprisedb.com