Skip site navigation (1) Skip section navigation (2)

Re: CREATE TABLE, load and freezing

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CREATE TABLE, load and freezing
Date: 2008-02-29 04:06:27
Message-ID: 2e78013d0802282006w69f8f032y1a1af3b376ec4aec@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-02-29 04:07:36
Subject: Re: Silly Newbie question
Previous:From: Tom LaneDate: 2008-02-29 04:03:31
Subject: Re: OSSP can be used in the windows environment now!

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group