| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Incorrect behaviour when using a GiST index on points |
| Date: | 2012-06-21 18:53:43 |
| Message-ID: | CAPpHfdvbkS6DAbM9uOJLUY6dNVZpunLTF8G1Yoj5ruKiVMPXcg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 22, 2012 at 5:56 PM, Alexander Korotkov <aekorotkov(at)gmail(dot)com>wrote:
> Attached patch fixes GiST behaviour without altering operators behaviour.
>
I think we definitely should apply this patch before 9.2 release, because
it is a bug fix. Otherwise people will continue produce incorrect GiST
indexes with in-core geometrical opclasses until 9.3. Patch is very simple
and only changes few lines of code.
Any thoughts?
------
With best regards,
Alexander Korotkov.
| Attachment | Content-Type | Size |
|---|---|---|
| gistproc_fix.patch | application/octet-stream | 2.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-06-21 19:47:09 | Re: foreign key locks |
| Previous Message | Tom Lane | 2012-06-21 18:37:16 | Re: Btree or not btree? That is the question |