Re: [PERFORM] Ignoring index on (A is null), (A is not null) conditions

[Cestmir Hybl]

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


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])

Re: [PERFORM] Response time

[Neil Conway]

On Tue, 2003-11-04 at 09:49, [EMAIL PROTECTED] wrote:
 How do we measure the response time in postgresql?

In addition to EXPLAIN ANALYZE, the log_min_duration_statement
configuration variable and the \timing psql command might also be
useful.

-Neil



---(end of broadcast)---
TIP 8: explain analyze is your friend