Re: Dead Space Map version 3 (simplified)

From: Hiroki Kataoka <kataoka(at)interwiz(dot)jp>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Dead Space Map version 3 (simplified)
Date: 2007-04-24 07:22:39
Message-ID: 462DB03F.2030803@interwiz.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Gregory Stark wrote:
> "Hiroki Kataoka" <kataoka(at)interwiz(dot)jp> writes:
>
>> I think there is no problem. Bloating will make pages including the
>> unnecessary area which will not be accessed. Soon, those pages will be
>> registered into DSM.
>
> Except the whole point of the DSM is to let us vacuum those pages *before*
> that happens...

You are right. However, expecting perfection will often lose
performance. Delaying processing to some extent leads to performance.

Even if hot page is not vacuumed, it does not mean generating dead
tuples boundlessly. About one hot page, the quantity of dead tuple
which continues existing unnecessarily is at most 1 page or its extent.
Also that page is soon registered into DSM by checkpoint like fail-safe.

Isn't some compromise need as first version of DSM vacuum?

--
Hiroki Kataoka <kataoka(at)interwiz(dot)jp>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-04-24 07:38:47 Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Previous Message Marcin Waldowski 2007-04-24 07:10:12 Re: BUG #3242: FATAL: could not unlock semaphore: error code 298

Browse pgsql-patches by date

  From Date Subject
Next Message Zeugswetter Andreas ADI SD 2007-04-24 08:08:44 Re: [HACKERS] Full page writes improvement, code update
Previous Message Tom Lane 2007-04-24 04:37:20 Re: BUG #3245: PANIC: failed to re-find shared loc k o b j ect