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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: table/index fillfactor control, try 2
Date: 2006-06-19 05:05:05
Message-ID: 20060619132856.9EA8.ITAGAKI.TAKAHIRO@oss.ntt.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> The disadvantage of putting this stuff into metapages is that then you
> need some entirely new protocol for letting clients get at it (and
> pg_dump, for one, needs to).

> An opaque bytea won't do though.  What I'd suggest is something real
> close to the format used for GUC parameters in ALTER DATABASE SET and
> ALTER USER SET, ie, pairs of keyword/value strings.

Ok, I'll consult the ALTER DATABASE SET codes.

Storing in arrays might make it difficult to retrieve relations that match
conditions specified by clients. However, I think such queirs are not used
so many times. And if necessary, we can provide a helper function to extract
a value from an array, like "valueof(reloptions, 'fillfactor') > 90"

---
ITAGAKI Takahiro
NTT Open Source Software Center



In response to

pgsql-hackers by date

Next:From: ITAGAKI TakahiroDate: 2006-06-19 05:36:28
Subject: Re: table/index fillfactor control, try 2
Previous:From: Tom LaneDate: 2006-06-19 03:55:09
Subject: Re: kill_prior_tuple for bitmap scan

pgsql-patches by date

Next:From: ITAGAKI TakahiroDate: 2006-06-19 05:36:28
Subject: Re: table/index fillfactor control, try 2
Previous:From: Andrew DunstanDate: 2006-06-18 23:14:11
Subject: Re: small regression script improvement

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