Decibel! wrote:
-- Start of PGP signed section.
> On Thu, Aug 09, 2007 at 09:57:48AM +0900, ITAGAKI Takahiro wrote:
> > > If HOT gets into 8.3, we might need a GUC to set database wide heap
> > > fillfactor to an appropriate value.
> >
> > I have no objection to do that, but we will need other def
On Thu, Aug 09, 2007 at 09:57:48AM +0900, ITAGAKI Takahiro wrote:
> > If HOT gets into 8.3, we might need a GUC to set database wide heap
> > fillfactor to an appropriate value.
>
> I have no objection to do that, but we will need other default values soon,
> something like default_[heap|btree|has
On Thu, 2007-08-09 at 12:17 +0530, Pavan Deolasee wrote:
> OK. I wish to have a config parameter so that DBA can set
> the system level default and then override that (if required) for
> each table. It will also be useful for experimenting with different
> fillfactor. The only way today is either
On 8/8/07, Simon Riggs <[EMAIL PROTECTED]> wrote:
>
>
> I see why you think that, but it is really just the first update that is
> cold. All further updates on that block will be able to re-use the dead
> row left by the first update. If they can't they will spread out to
> other blocks where they
"Pavan Deolasee" <[EMAIL PROTECTED]> wrote:
> If HOT gets into 8.3, we might need a GUC to set database wide heap
> fillfactor to an appropriate value.
I have no objection to do that, but we will need other default values soon,
something like default_[heap|btree|hash|gist|gin]_fillfactor. Some o
On Wed, 2007-08-08 at 18:05 +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 tupl
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 tu
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 UPDAT
