| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Cc: | 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 13:25:03 |
| Message-ID: | 20070814132503.GC9206@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Oleg Bartunov wrote:
> On Thu, 9 Aug 2007, tomas(at)tuxteam(dot)de wrote:
>
>> Maybe I'm missing something, but it seems to me that the configuration
>> is more attached to a column/index thatn to the whole database. If
>> there's a default in an expression, I'd rather expect this default to be
>> drawn from the index involved than from a global value (like a functional
>> index does now).
>
> 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?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-08-14 14:19:03 | Re: default_text_search_config and expression indexes |
| Previous Message | Luke Lonergan | 2007-08-14 08:10:45 | Re: L |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-08-14 13:55:27 | Re: Testing the async-commit patch |
| Previous Message | Alvaro Herrera | 2007-08-14 13:11:27 | Re: Testing the async-commit patch |