On Wed, Sep 9, 2020 at 3:09 PM Heikki Linnakangas <hlinn...@iki.fi> wrote:
> On 09/09/2020 13:28, Andrey M. Borodin wrote: > > Thanks Darafei! > > > >> 9 сент. 2020 г., в 12:05, Darafei Komяpa Praliaskouski > >> <m...@komzpa.net> написал(а): > >> > >>> How does the 'sortsupport' routine interact with > >>> 'compress'/'decompress'? Which representation is passed to the > >>> comparator routine: the original value from the table, the > >>> compressed representation, or the decompressed representation? Do > >>> the comparetup_index_btree() and readtup_index() routines agree > >>> with that? > >> > .... > > Come to think of it, the point z-order comparator could benefit a lot > from key abbreviation, too. You could do the point -> zorder conversion > in the abbreviation routine. > That's how it works in PostGIS, only that we moved to more effecient Hilbert curve: https://github.com/postgis/postgis/blob/54399b9f6b0f02e8db9444f9f042b8d4ca6d4fa4/postgis/lwgeom_btree.c#L171
