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

Re: Aggressive freezing in lazy-vacuum

From: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Aggressive freezing in lazy-vacuum
Date: 2007-03-07 02:18:20
Message-ID: 20070307110352.5E09.ITAGAKI.TAKAHIRO@oss.ntt.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patchespgsql-performance
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I said nothing about expired tuples.  The point of not freezing is to
> preserve information about the insertion time of live tuples.

I don't know what good it will do -- for debugging?
Why don't you use CURRENT_TIMESTAMP?


> And your
> test case is unconvincing, because no sane DBA would run with such a
> small value of vacuum_freeze_min_age.

I intended to use the value for an accelerated test.
The penalties of freeze are divided for the long term in normal use,
but we surely suffer from them by bits.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center



In response to

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2007-03-07 04:34:57
Subject: Re: Aggressive freezing in lazy-vacuum
Previous:From: Merlin MoncureDate: 2007-03-07 02:12:03
Subject: Re: compact flash disks?

pgsql-hackers by date

Next:From: Jeff DavisDate: 2007-03-07 02:28:30
Subject: Re: Bug: Buffer cache is not scan resistant
Previous:From: Jeff DavisDate: 2007-03-07 02:10:17
Subject: Re: Bug: Buffer cache is not scan resistant

pgsql-patches by date

Next:From: Trevor HardcastleDate: 2007-03-07 03:06:29
Subject: CREATE TABLE LIKE INCLUDING INDEXES support
Previous:From: ITAGAKI TakahiroDate: 2007-03-07 01:56:04
Subject: Re: Aggressive freezing in lazy-vacuum

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