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

Re: table/index fillfactor control, try 2

From: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: table/index fillfactor control, try 2
Date: 2006-06-19 05:36:28
Message-ID: 20060619132631.9EA5.ITAGAKI.TAKAHIRO@oss.ntt.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:

> >  2. Store the structures in AM's meta page. But heaps don't have meta pages.
> 
> But perhaps they should? That sounds very similar to the idea of
> non-transactional pg_class data.

Presently, I suppose the parameters are not modified so many times.
They are set only on build time or maintenance.

I think we will need metapages in the future, but not right now. If we will
provide an automatic configurator for fillfactors (or other parameters),
parameters might be changed every time the configurator runs, for example,
per autovacuum.


> The metagpages thought would require some consolidation from various
> other proposals, so we'll need to wait for wider discussion on that.

I agree, but it is easy to move the metadata from catalog to metapages.
So the metapages thought can be reconciled among proposals that must need it.
(pg_class_nt and dead tuples bitmaps?)

---
ITAGAKI Takahiro
NTT Open Source Software Center



In response to

Responses

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2006-06-19 05:46:30
Subject: sync_file_range()
Previous:From: ITAGAKI TakahiroDate: 2006-06-19 05:05:05
Subject: Re: table/index fillfactor control, try 2

pgsql-patches by date

Next:From: Simon RiggsDate: 2006-06-19 08:31:41
Subject: Re: table/index fillfactor control, try 2
Previous:From: ITAGAKI TakahiroDate: 2006-06-19 05:05:05
Subject: Re: table/index fillfactor control, try 2

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