From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Cube extension kNN support |
Date: | 2015-12-15 18:46:03 |
Message-ID: | 56705FEB.7080607@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 12/07/2015 03:47 PM, Stas Kelvich wrote:
> Hello, fixed.
I've looked at the patch today, seems mostly fine to me.
Three comments though:
1) (nitpicking) There seem to be some minor whitespace issues, i.e.
trailing spaces, empty lines being added/removed, etc.
2) one of the regression tests started to fail
SELECT '-1e-700'::cube AS cube;
This used to return (0) but now I get (-0). As this query existed in
1.0, it's probably due to change in the C code. Now sure where.
3) I wonder why the docs were changed like this:
<para>
- It does not matter which order the opposite corners of a cube are
- entered in. The <type>cube</> functions
- automatically swap values if needed to create a uniform
- <quote>lower left — upper right</> internal representation.
+ When corners coincide cube stores only one corner along with a
special flag in order to reduce size wasted.
</para>
Was the old behavior removed? I don't think so - it seems to behave
as before, so why to remove this information? Maybe it's not useful?
But then why add the bit about optimizing storage of points?
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-12-15 18:56:30 | Re: [PATCH] Refactoring of LWLock tranches |
Previous Message | Andres Freund | 2015-12-15 18:04:22 | Re: _mdfd_getseg can be expensive |