Nichlas =?iso-8859-1?Q?L=F6fdahl?= <[EMAIL PROTECTED]> writes:
> I have a partial index (btree(col)  WHERE col > 0) on table2 ('col' contains 
> alot of NULL-values).

> There's also a foreign key on the column pointing to the primary key of 
> table1 (ON UPDATE CASCADE ON DELETE SET NULL). During update/delete, it seems 
> like it cannot use the partial index to find corresponding rows matching the 
> foreign key (doing a full seqscan instead)? 

> Is there any special reason for not letting the planner use the partial index 
> when appropriate? 

It doesn't know it's appropriate.  There's nothing constraining the FK
to be positive, after all.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Reply via email to