RE: slow join on postgresql6.5 - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject RE: slow join on postgresql6.5
Date
Msg-id 002101bf9af8$b085f840$2801007e@tpf.co.jp
Whole thread Raw
In response to Re: slow join on postgresql6.5  (Don Baccus <dhogaza@pacifier.com>)
Responses RE: slow join on postgresql6.5  (Don Baccus <dhogaza@pacifier.com>)
List pgsql-hackers
> -----Original Message-----
> From: majordomo-owner@hub.org [mailto:majordomo-owner@hub.org]On Behalf
> Of Don Baccus
> 
> Whatever ... in this particular case  - referential integrity 
> with MATCH <unspecified> and MATCH PARTIAL and multi-column
> foreign keys - performance will likely drop spectacularly once the
> leading column is NULL, while (say) with Oracle you'd expect much
> less of a performance hit. 
>

As for NULL,it seems possible to look up NULL keys in a btree index
because NULL == NULL for btree indexes.
I've wondered why PostgreSQL's planner/executor never looks up
indexes for queries using 'IS NULL'.

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp 


pgsql-hackers by date:

Previous
From: "Sergey V. Mikheev"
Date:
Subject: Postresql & triggers
Next
From: Michael Meskes
Date:
Subject: Re: BIT datatype