| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Incorrect behaviour when using a GiST index on points |
| Date: | 2012-07-03 15:34:24 |
| Message-ID: | 7948.1341329664@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Jun 21, 2012 at 2:53 PM, Alexander Korotkov
> <aekorotkov(at)gmail(dot)com> wrote:
>> 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?
> Do we need to apply this patch to 9.2?
It's been like that all along, no? I'm feeling hesitant to shove it
into 9.2 at this late date. But we should review it and get it into
9.3 early if possible.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-07-03 15:35:57 | Re: [Review] Prevent the specification of conflicting transaction read/write options |
| Previous Message | Robert Haas | 2012-07-03 15:33:20 | Re: [Review] Add SPI_gettypmod() to return a field's typemod from a TupleDesc |