Re: concurrent index builds unneeded lock?

On 7/11/09 3:50 AM, Greg Stark wrote:
> Hm. Actually maybe not. What if the index is an expression index and
> the expression includes a function which does an SQL operation? I'm
> not sure how realistic that is since to be a danger that SQL operation
> would have to be an insert, update, or delete which is not just
> bending the rules.

It's not realistic at all.  People are only supposed to use IMMUTABLE 
functions for experession indexes; if they declare a volatile function 
as immutable, then it's their own lookout if they corrupt their data.

-- 
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com