From: | Decibel! <decibel(at)decibel(dot)org> |
---|---|
To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GUC for default heap fillfactor |
Date: | 2007-08-08 17:07:19 |
Message-ID: | 20070808170719.GH20424@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Aug 08, 2007 at 06:05:06PM +0530, Pavan Deolasee wrote:
> If HOT gets into 8.3, we might need a GUC to set database wide heap
> fillfactor to an appropriate value. The only way to so today is compile
> time value of DEFAULT_HEAP_FILLFACTOR. HOT works much
> better if there is atleast one tuple worth of free space in each block.
> Otherwise atleast the first UPDATE in each block would be a COLD
> update.
>
> Should we consider adding such a GUC now ? I searched through
> archives, but did not find any strong objection to doing so in the past.
> But I might have missed something. Comments ?
ISTM if we add one for tables we should add one for indexes as well...
Or do we want different fill factors for different index methods?
--
Decibel!, aka Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Decibel! | 2007-08-08 17:18:44 | Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions] |
Previous Message | Michael Glaesemann | 2007-08-08 17:03:34 | Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions] |