| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Florian Weimer <fweimer(at)bfk(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: Range Types |
| Date: | 2011-01-07 17:33:29 |
| Message-ID: | 1294421609.18031.3551.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2011-01-07 at 08:21 +0000, Florian Weimer wrote:
> <http://www.postgresql.org/docs/8.4/static/xoper-optimization.html>
>
> I'm wondering if one of these hint functions can be reused to compute
> range lengths.
Interesting idea.
However, I don't really see a way to make that work. These functions are
tied to the operator, so it would be awkward to try to connect it to the
GiST support functions. Also, it doesn't seem to be an exact fit,
because the RESTRICT function is used to compute the selectivity as of
right now using current statistics.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2011-01-07 17:37:35 | Re: [COMMITTERS] pgsql: Implement remaining fields of information_schema.sequences view |
| Previous Message | Jehan-Guillaume (ioguix) de Rorthais | 2011-01-07 17:21:48 | Re: some comments rewording in recovery.conf.sample about SR |