Re: plpgsql functions and NULLs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Don Drake <dondrake(at)gmail(dot)com>
Cc: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, pgsql-sql(at)postgresql(dot)org
Subject: Re: plpgsql functions and NULLs
Date: 2005-02-01 03:37:05
Message-ID: 9324.1107229025@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Don Drake <dondrake(at)gmail(dot)com> writes:
> On Mon, 31 Jan 2005 16:32:02 -0800 (PST), Stephan Szabo
> <sszabo(at)megazone(dot)bigpanda(dot)com> wrote:
>> Actually, now that I think about it, I wonder if that's a good thing to
>> use because I don't think that'll use indexes to do the search. You may
>> want to do some testing to see how it runs for you.

> I'm constraining on other columns as well and it's still picking up the index.

Stephan is right that an IS DISTINCT FROM construct is not considered
indexable. So it's only your other constraints that are being used
with the index. You need to think about whether the other constraints
are selective enough to yield adequate performance.

regards, tom lane

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Dennis Sacks 2005-02-01 03:51:06 Re: BLOBs vs BYTEA
Previous Message Sam Adams 2005-02-01 02:26:30 BLOBs vs BYTEA