Message-ID: <54EDD887.8030703@vmware.com>
Date: Wed, 25 Feb 2015 16:13:27 +0200
From: Heikki Linnakangas <hlinnakangas@vmware.com>
Organization: VMware
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: Teodor Sigaev <teodor@sigaev.ru>, Pgsql Hackers
 <pgsql-hackers@postgresql.org>
Subject: Re: compress method for spgist - 2
References: <54907069.1030506@sigaev.ru> <54993A76.7050308@vmware.com>
 <54DE237E.4000207@sigaev.ru>
In-Reply-To: <54DE237E.4000207@sigaev.ru>
Content-Type: text/plain; charset="koi8-r"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 02/13/2015 06:17 PM, Teodor Sigaev wrote:
>> Now that the input data type and leaf data type can be different, which one is
>> "attType"? It's the leaf data type, as the patch stands. I renamed that to
>> attLeafType, and went fixing all the references to it. In most places it's just
>> a matter of search & replace, but what about the reconstructed datum? In
>
> Done. Now there is separate attType and attLeafType which describe input/output
> and leaf types.

Thanks.

Did you try finding a use case for this patch in one of the built-in or 
contrib datatypes? That would allow writing a regression test for this.

In the original post on this, you mentioned that the PostGIS guys 
planned to use this to store polygons, as bounding boxes 
(http://www.postgresql.org/message-id/5447B3FF.2080406@sigaev.ru). Any 
idea how would that work?

- Heikki


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers