Re: CREATE TABLE, load and freezing

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CREATE TABLE, load and freezing
Date: 2008-02-28 10:16:50
Message-ID: 2e78013d0802280216of79c5fcw9a04fbedf14b2e1d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 28, 2008 at 3:25 PM, ITAGAKI Takahiro
<itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> wrote:
>
>
> Sounds cool. I recommended users to do VACUUM FREEZE just after initial
> loading, but we can avoid it with your method.
>

Yeah, and the additional step of VACUUM FREEZE adds up to the restore
time.

>
> To make things worse, the freezing day comes at once because the first restore
> is done in a single or near transactions; The wraparound timings of many
> tables are aligned at the same time. Freezing copy will be the solution.
>

If we can start with a freezed table and even if the table is
subsequently updated,
hopefully DSM (or something of that sort) will help us reduce the vacuum freeze
time whenever its required.

Thanks,
Pavan

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2008-02-28 10:20:21 Re: CREATE TABLE, load and freezing
Previous Message Pavan Deolasee 2008-02-28 10:01:00 Re: CREATE TABLE, load and freezing