| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Cc: | "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>, <tomas(at)tuxteam(dot)de>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: default_text_search_config and expression indexes |
| Date: | 2007-08-14 14:19:03 |
| Message-ID: | 87eji66vxk.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
"Alvaro Herrera" <alvherre(at)commandprompt(dot)com> writes:
> Oleg Bartunov wrote:
>>
>> I'm tired to repeat - index itself doesn't know about configuration !
>
> Is there a way to change that? For example store the configuration in a
> metapage or something?
I think Heikki's suggestion of having each configuration create a new type
would effectively do the same thing.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2007-08-14 14:31:30 | Re: L |
| Previous Message | Alvaro Herrera | 2007-08-14 13:25:03 | Re: default_text_search_config and expression indexes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-08-14 14:26:24 | Re: Question about change in page/tuple header (v4) |
| Previous Message | Andrew Dunstan | 2007-08-14 14:13:20 | Re: Testing the async-commit patch |