Re: Performance problem in textanycat/anytextcat

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Performance problem in textanycat/anytextcat
Date: 2010-05-16 15:57:35
Message-ID: 2350.1274025455@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> Marking textanycat as not immutable would forbid using it in
>> expression indexes, too.

> True. On the other hand, the current state of affairs allows one to
> create an index on expressions that aren't really immutable, with
> ensuing hilarity.

It strikes me that we could avoid any possible functional regression
here by having CREATE INDEX perform expression preprocessing (in
particular, function inlining) before it tests to see if the index
expression contains any non-immutable functions.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2010-05-16 16:04:15 Re: [PATCH] Add SIGCHLD catch to psql
Previous Message Simon Riggs 2010-05-16 15:53:32 Re: Keepalive for max_standby_delay