| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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-08-28 02:21:27 |
| Message-ID: | 20120828022127.GE6786@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 27, 2012 at 07:43:49PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I need someone to review this patch for 9.3. We have already missed
> > fixing this for 9.2.
>
> So put it in the next commitfest.
Done. I have linked to your comment below too.
---------------------------------------------------------------------------
> FWIW, I looked at this last week, and concluded I didn't have enough
> confidence in it to push it into 9.2 at the last minute.
>
> There's also the big-picture question of whether we should just get rid
> of fuzzy comparisons in the geometric types instead of trying to hack
> indexes to work around them. I'd really rather have us debate that
> question and resolve it one way or the other before spending time on the
> details of patches that take the second approach.
>
> regards, tom lane
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2012-08-28 02:36:58 | Re: Advisory Lock BIGINT Values |
| Previous Message | Bruce Momjian | 2012-08-28 02:20:29 | Re: Incorrect behaviour when using a GiST index on points |