From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Why is box <-> point missing, and box <-> box not indexable? |
Date: | 2016-08-12 15:27:38 |
Message-ID: | 29207.1471015658@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> point <-> point, circle <-> point and polygon <-> point all exist as
> orderable-by-operator operators (in fact they are the only ones by
> default). But there's no box <-> point operator at all, and no index
> support for box <-> box.
> Was this intentional, or just a strange oversight?
Seems like an oversight. None of these operators have commutators,
but it seems like they all should:
<->(point,line)
<->(point,lseg)
<->(point,box)
<->(lseg,line)
<->(lseg,box)
<->(point,path)
<->(circle,polygon)
<->(line,box)
Dunno about the index-support angle.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-08-12 15:35:19 | Re: Fwd: [BUG] Print timing statistics of trigger execution under turned off timing option of EXPLAIN ANALYZE |
Previous Message | Andrew Gierth | 2016-08-12 15:02:12 | Why is box <-> point missing, and box <-> box not indexable? |