|From:||Teodor Sigaev <teodor(at)sigaev(dot)ru>|
|To:||Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: compress method for spgist - 2|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> For some datatypes, the compress method might be useful even if the leaf
> type is the same as the column type. For example, you could allow
> indexing text datums larger than the page size, with a compress function
> that just truncates the input.
Agree, and patch allows to use compress method in this case, see begining of
> Could you find some use for this in one of the built-in or contrib
> types? Just to have something that exercises it as part of the
> regression suite. How about creating an opclass for the built-in polygon
> type that stores the bounding box, like the PostGIS guys are doing?
Will try, but I don't have nice idea. Polygon opclass will have awful
performance until PostGIS guys show the tree structure.
> The documentation needs to be updated.
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
|Next Message||Josh Berkus||2014-12-16 18:13:16||Re: Commitfest problems|
|Previous Message||Stephen Frost||2014-12-16 17:07:59||Re: 9.5 release scheduling (was Re: logical column ordering)|