Tom Lane <[EMAIL PROTECTED]> wrote:
> > CREATE INDEX foo ON bar (x) WITH (fillfactor = 70, option = blah);
>
> Yeah, something along this line is what I'd like to see; probably the
> first form since that creates the least hazard of foreclosing other
> additions to the syntax later.
> Anyway the bottom line is that we need to put in some infrastructure
> that can handle multiple index parameters, not a one-off solution that
> only handles PCTFREE.
Ok, I'll rewrite my PCTFREE patch, and change the word PCTFREE to FILLFACTOR.
There is no benefit of compatibility with Oracle now.
Current all index access methods (btree, hash and gist) have conception of
fillfactors, but static bitmap index or something may not have it.
I see that we should give priority to the design.
---
ITAGAKI Takahiro
NTT Cyber Space Laboratories
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
