From: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Subject: | Re: passing parameters to CREATE INDEX |
Date: | 2006-07-12 04:57:15 |
Message-ID: | 20060712125231.E855.ITAGAKI.TAKAHIRO@oss.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
> pluggable parameters for index.
> I think, we may
> can add to pg_opclass's definition method/parameter name and create some API
> (may be, index specific) to propagate parameter's to module's interface
> functions to index.
How abount adding a new option hander to GiST/GIN support functions?
Presently, amoptions() are defined as
bytea *amoptions (ArrayType *reloptions, bool validate).
If there is a support function like this form in operator classes,
we can propagate options. Eventually, calling sequence will be
DefineIndex() -> amoptions() -> tsvectoroptions().
We also need to change gist/ginoptions() in order to determine what operator
class is used. This is a bit messy problem. Options are parsed before support
functions are initialized, so that I don't know in what form we should pass the
operator class to amoptions().
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2006-07-12 05:18:09 | Re: newbie patch-attempt: selecting large result sets in |
Previous Message | Greg Stark | 2006-07-12 04:44:29 | Re: [PATCHES] putting CHECK_FOR_INTERRUPTS in qsort_comparetup() |