| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: table/index fillfactor control |
| Date: | 2006-06-06 11:54:14 |
| Message-ID: | 1149594854.2621.431.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Tue, 2006-06-06 at 18:02 +0900, ITAGAKI Takahiro wrote:
> This is a patch for table/index fillfactor control
This is a good new feature and I'll vote for it.
I see what Tom was driving at with earlier comments. I think we need an
non-index AM specific patch, so that each AM has its own parameters.
So we have a new element of the RelationData struct:
void *rd_amopts;
Which each AM defines and interprets.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kenneth Marshall | 2006-06-06 11:58:10 | Re: Duplicate rows sneaking in despite PRIMARY KEY / UNIQUE constraint |
| Previous Message | Simon Riggs | 2006-06-06 11:10:45 | Re: fillfactor using WITH syntax |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2006-06-06 13:53:25 | Re: table/index fillfactor control |
| Previous Message | Simon Riggs | 2006-06-06 11:19:54 | Re: 'Index Full Scan' for Index Scan without Index Cond |