Re: Problemas with gram.y

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jaime Casanova" <systemguards(at)gmail(dot)com>
Cc: tmorelli(at)tmorelli(dot)com(dot)br, pgsql-hackers(at)postgresql(dot)org, etmorelli(at)superig(dot)com(dot)br
Subject: Re: Problemas with gram.y
Date: 2006-03-04 06:16:55
Message-ID: 11785.1141453015@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Jaime Casanova" <systemguards(at)gmail(dot)com> writes:
> On 3/3/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I find the whole idea pretty ugly myself.

> why? if i can ask? you didn't seem upset with that in the thread

What's bugging me about it is that the proposed syntax wedges a bunch
of index-access-method-specific parameters into what ought to be an
access-method-agnostic syntax; and furthermore does it by adding more
grammar keywords, something we have far too many of already. There are
direct measurable costs to having more keywords, and the approach does
not scale up to allowing other index AMs to have other parameters that
might not bear at all on btree.

I don't object to the concept of providing some way of adjusting index
fill factors, but I'm not at all happy with doing it like this. I'd
like to see a design that has some extensibility to it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Md.Abdul Aziz 2006-03-04 06:38:52 Deleting loid from the database
Previous Message Jaime Casanova 2006-03-04 05:48:52 Re: Problemas with gram.y