Re: compress method for spgist - 2
Alexander Korotkov <aekorotkov@gmail.com>
From: Alexander Korotkov <aekorotkov@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Darafei Komяpa Praliaskouski <me@komzpa.net>, Nikita Glukhov <n.gluhov@postgrespro.ru>, pgsql-hackers <pgsql-hackers@postgresql.org>, Heikki Linnakangas <hlinnaka@iki.fi>, Fedor Sigaev <teodor@sigaev.ru>
Date: 2017-09-21T08:27:47Z
Lists: pgsql-hackers
On Thu, Sep 21, 2017 at 3:14 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Alexander Korotkov <aekorotkov@gmail.com> writes: > > On Thu, Sep 21, 2017 at 2:06 AM, Darafei "Komяpa" Praliaskouski < > >> It seems to me that any circle with radius of any Infinity should > become a > >> [-Infinity .. Infinity, -Infinity .. Infinity] box.Then you won't have > >> NaNs, and index structure shouldn't be broken. > > > We probably should produce [-Infinity .. Infinity, -Infinity .. Infinity] > > box for any geometry containing inf or nan. > > Hm, we can do better in at least some cases, eg for a box ((0,1),(1,inf)) > there's no reason to give up our knowledge of finite bounds for the > other three boundaries. But certainly for a NaN circle radius > what you suggest seems the most sensible thing to do. > OK. I'll try implement this for circles. ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Commits
-
Doc: remove duplicate poly_ops row from SP-GiST opclass table.
- d3b851e9a3c9 11.0 landed
-
Add polygon opclass for SP-GiST
- ff963b393ca9 11.0 landed