From: Cestmir Hybl <cestmirl@freeside.sk>
To: pgsql-performance@postgresql.org
Subject: Re: Ignoring index on (A is null), (A is not null) conditions
Date: Tue, 4 Nov 2003 11:43:51 +0100
Message-ID: <00e201c3a2c0$89409f00$0200a8c0@stratos> (raw)
References: <017201c39d85$533eed70$0200a8c0@stratos>
First of all, thanks for all your suggestions.
They were of two classes:
1. use different data representation (special constant from column domain
instead of NULL)
This is possible, of course, but it makes data model less portable and
requires changes in database abstraction layer of application.
2. use partial indexes
This is suitable for single null-allowed column index. With increasing
number of null-allowed columns inside index, the number of partial indexes
required grows exponentially.
All RDBMSs I ever used (Sybase, MSSQL, or even MySQL) were using index to
filter by expressions containing is NULL conditions /(A is NULL), (A is not
NULL), (A is NULL or A = const), (A is NULL or A > const)/ so it seems
pretty strange to me that PostgreSQL does not.
Is this sheduled feature at least?
CH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: cestmirl@freeside.sk
Subject: Re: Ignoring index on (A is null), (A is not null) conditions
In-Reply-To: <00e201c3a2c0$89409f00$0200a8c0@stratos>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox