mirror of
https://github.com/postgres/postgres.git
synced 2026-07-16 23:05:04 -04:00
I found another bug in btree index. Looking at the code it seems that NULL
keys are never used to build or scan a btree index (see the explain commands
in the example). However this is not the case when a null key is retrieved
in an outer loop of a join select and used in an index scan of an inner loop.
This bug causes at least three kinds of problems:
1) the backend crashes when it tries to compare a text string with a null.
2) it is not possible to find tuples with null keys in a join.
3) null is considered equal to 0 when the datum is passed by value, see
the last query.
Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
|
||
|---|---|---|
| .. | ||
| backend | ||
| bin | ||
| include | ||
| interfaces | ||
| mk | ||
| test | ||
| tools/mkldexport | ||
| tutorial | ||
| MAKE_CTAGS | ||
| MAKE_MKID | ||
| Makefile | ||
| Makefile.global | ||