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

Re: Error correction for n_dead_tuples

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Error correction for n_dead_tuples
Date: 2007-09-26 08:23:20
Message-ID: 200709260823.l8Q8NKa05660@momjian.us (view raw or flat)
Thread:
Lists: pgsql-patches
This patch is no longer needed.  We can revisit this during 8.4 to see
if it is still needed now that we have HOT.

---------------------------------------------------------------------------

ITAGAKI Takahiro wrote:
> Here is a patch discussed in
> http://archives.postgresql.org/pgsql-hackers/2007-02/msg00010.php
> 
> Concurrent vacuum will save n_dead_tuples value at the beginning.
> Stats collector will be subtract the value from n_dead_tuples
> instead of setting it to zero. The statistics accuracy of n_dead_tuples
> will be better, especially just after finish of a vacuum.
> 
> The behavior in VACUUM FULL is not changed because concurrent updates
> are not allowed during VACUUM FULL.
> 
> Comments welcome.
> 
> Regards,
> ---
> ITAGAKI Takahiro
> NTT Open Source Software Center

[ Attachment, skipping... ]

> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-patches by date

Next:From: Bruce MomjianDate: 2007-09-26 08:25:28
Subject: Re: Recalculating OldestXmin in a long-running vacuum
Previous:From: Tom RaneyDate: 2007-09-26 04:53:55
Subject: Hash Index Build Patch

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