| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Review: B-Tree emulation for GIN |
| Date: | 2009-01-19 18:02:40 |
| Message-ID: | 1232388160.7281.129.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2009-01-19 at 20:15 +0300, Teodor Sigaev wrote:
> Changes:
> - use NULL as left-most value. It's safe because NULL numeric value
> cannot be an argument for any function except gin_numeric_cmp and it
> cannot be returned in regular SQL query.
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).
I know you mean a C NULL, not a SQL NULL, but it reminded me to test SQL
NULL.
And how does GIN handle SQL NULL values in the column? Does it index
them at all, or just ignore them?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2009-01-19 18:15:57 | Re: [PATCHES] GIN improvements |
| Previous Message | Tom Lane | 2009-01-19 18:00:26 | Re: [PATCHES] GIN improvements |