Skip site navigation (1) Skip section navigation (2)

Re: Problem with index in OR'd expression

From: Ragnar <gnari(at)hive(dot)is>
To: postgresql(dot)org(at)tgice(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem with index in OR'd expression
Date: 2006-12-27 17:27:50
Message-ID: 1167240470.6369.328.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-general
On miĆ°, 2006-12-27 at 11:02 -0600, postgresql(dot)org(at)tgice(dot)com wrote:
> I was referring to the situation where one has this in a WHERE clause:
>    ((vConstant IS NULL) OR (Table.IndexedCol = vConstant))
> where vConstant is a *constant* parameter in a pl/pgsql function.

Reguardless of the issue whether pl/pgsql could be expected to
optimize this case, I find it difficult to imagine a scenario
where this kind of coding makes sense.

I understand that in some cases on would like to do this with
a *variable* to simplify logic, but what possible gain can
be had from doing this with a constant, other that obfuscation?

It does not make sense to spend CPU-time on  optimizing a case
that is not useful or common.


In response to


pgsql-general by date

Next:From: Tom LaneDate: 2006-12-27 17:45:10
Subject: Re: Problem with index in OR'd expression
Previous:From: A. KretschmerDate: 2006-12-27 17:03:29
Subject: Re: Is PostgreSQL for this?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group