Re: [PERFORM] Index order ignored after `is null` in query

Hi, thanks for your time and answer. Not treating IS NULL as equality operator definitely helps me to make more sense out of previous explains. -- Best Regard, Artūras Lapinskas On Thu, Nov 06, 2014 at 12:23:12PM -0500, Tom Lane wrote: =?utf-8?Q?Art=C5=ABras?= Lapinskas arturasl

Re: [PERFORM] Index order ignored after `is null` in query

bitmap index. Sadly bitmaps tend to be not the best option when using limit in queries. Which would make sense, if it is really a need to synchronize index with relation... -- Best Regard, Artūras Lapinskas On Wed, Nov 05, 2014 at 10:42:43PM +0100, Artūras Lapinskas wrote: Hello, I am having

[PERFORM] Index order ignored after `is null` in query

using `select version()` = PostgreSQL 9.3.5 on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.7.2-5) 4.7.2, 64-bit, compiled from source with no default configuration changes. -- Best Regard, Artūras Lapinskas -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org

[PERFORM] Index order ignored after `is null` in query

Hello, I am having some hard time understanding how postgresql handles null values. As much I understand null values are stored in b-tree as simple values (put as last or first depending on index). But it seems that there is something really specific about them as postgresql deliberately