From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: fillfactor using WITH syntax |
Date: | 2006-06-06 15:00:36 |
Message-ID: | 1149606036.2621.511.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Tue, 2006-06-06 at 10:27 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > Why not implement an array of option parameters on pg_class, so both
> > heaps and indexes can be given additional parameters? That way you
> > wouldn't need a specific relfillfactor attribute. That would allow us to
> > keep CREATE TABLE free of additional keywords also.
>
> None of this should go anywhere near pg_class. IIRC the solutions we
> discussed involved adding some sort of array to pg_index.
Itagaki had suggested adding options to heaps also, so clearly we'd need
to add that to pg_class, rather than pg_index in that case.
PCTFREE would be useful for heaps as well as indexes, but there could be
other options also. Extending the thought for the general case, I see no
reason why we would want to permanently exclude heaps from having a more
flexible set of options when we aim to provide that for indexes.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Travis Cross | 2006-06-06 15:32:04 | Re: Duplicate rows sneaking in despite PRIMARY KEY / UNIQUE |
Previous Message | Ian Barwick | 2006-06-06 14:58:38 | Re: Duplicate rows sneaking in despite PRIMARY KEY / UNIQUE constraint |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2006-06-06 15:03:44 | Re: 'Index Full Scan' for Index Scan without Index Cond |
Previous Message | Tom Lane | 2006-06-06 14:59:59 | Re: Why do we have a WAL record for CLOG page extension? |