> gin_numeric_cmp() can be called from regular SQL. I missed this before,
> but that function will segfault if you call gin_numeric_cmp(NULL, 1) (in
> v0.7 at least).
Fixed, gin_numeric_cmp is marked as strict.
> And how does GIN handle SQL NULL values in the column? Does it index
> them at all, or just ignore them?
SQL NULL: GIN doesn't support it (amindexnulls/amsearchnulls == false)
C NULL: NULL-numeric could be returned only by gin_extract_query_numeric which
cannot be called by user directly because of internal type of argument.
GIN doesn't do anything with values returned by gin_extract_query_numeric except
providing they as an argument for comparing functions.
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
In response to
pgsql-hackers by date
|Next:||From: Teodor Sigaev||Date: 2009-01-19 18:45:32|
|Subject: Re: tsearch with Turkish locale ( was Re: foreign_data
test fails with non-C locale)|
|Previous:||From: Devrim GÜNDÜZ||Date: 2009-01-19 18:20:26|
|Subject: Re: tsearch with Turkish locale ( was Re: foreign_datatest fails with non-C locale)|