| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | YAMAMOTO Takashi <yamt(at)mwd(dot)biglobe(dot)ne(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ordering op for WHERE |
| Date: | 2012-01-04 02:13:57 |
| Message-ID: | CA+TgmoYv7_4Trv=wJzJAu=NTomFo50G-K72JE6bH7n0u4YOcNA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 27, 2011 at 10:48 PM, YAMAMOTO Takashi
<yamt(at)mwd(dot)biglobe(dot)ne(dot)jp> wrote:
> does it make sense to teach the planner (and the executor?) use an ordering op
> to optimize queries like the following?
>
> select * from t where a <-> 1000 < 10
Seems useful to me. I'm not sure how hard it is, though.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-01-04 02:18:02 | Re: Re: [COMMITTERS] pgsql: pg_regress: Replace exit_nicely() with exit() plus atexit() hook |
| Previous Message | Andrew Dunstan | 2012-01-04 02:11:17 | Re: Add SPI results constants available for PL/* |