Re: avoiding seq scan without duplicating - Mailing list pgsql-general

From Andrus
Subject Re: avoiding seq scan without duplicating
Date
Msg-id 08886572B8D0410B88857161F79A561A@andrusnotebook
Whole thread Raw
In response to Re: avoiding seq scan without duplicating  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom,

> The proposed transformation is not correct because of the odd behavior
> of NOT IN with respect to nulls.

Thank you.

In this particular case dokumnr is dok table primary key of type int.
bilkaib.dokumnr can contain nulls but this does not affect to result
probably.

So in this case this conversion is probably correct.

Andrus.


pgsql-general by date:

Previous
From: Gerhard Heift
Date:
Subject: Re: UPDATE tuples with a sub-select
Next
From: Thomas Kellerer
Date:
Subject: Re: UPDATE tuples with a sub-select