| From: | Decibel! <decibel(at)decibel(dot)org> |
|---|---|
| To: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GUC for default heap fillfactor |
| Date: | 2007-08-09 14:53:24 |
| Message-ID: | 20070809145324.GM20424@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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|hash|gist|gin]_fillfactor. Some of us
> might feel it is mess to add random guc variables.
I think we'd want to handle indexes with a different mechanism, probably
one that makes changes to pg_am.
In any case, how important is it to do this before 8.3? We were supposed
to release this month, after all.
--
Decibel!, aka Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hans-Juergen Schoenig | 2007-08-09 14:54:33 | Re: crypting prosrc in pg_proc |
| Previous Message | Zdenek Kotala | 2007-08-09 14:50:53 | Re: crypting prosrc in pg_proc |