| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Subject: | Re: passing parameters to CREATE INDEX |
| Date: | 2006-07-05 13:35:03 |
| Message-ID: | 2898.1152106503@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
> 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.
Huh? You can get them from the index's Relation structure. I don't
think there's anything missing in the API. About all you need is an
extended struct definition for rd_options, and to provide your own code
substituting for default_reloptions(). An index AM can do both of those
locally to itself.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phil Frost | 2006-07-05 13:47:20 | set search_path in dump output considered harmful |
| Previous Message | Teodor Sigaev | 2006-07-05 13:17:48 | Re: passing parameters to CREATE INDEX |