[postgis-devel] Bit setting to compress PostGIS geometries

[Daniel Baston]

Agreed, nothing will be compressed if the user selects an incompressible
storage type. We could use a function name that describes exactly what it
does ("postgis_zero_out_bits_not_required_to_maintain_specified_precision")
but I don't think that really creates less confusion (for one, it doesn't
convey why you would want to do this). I'm very open to other ideas, though.

Dan

On Wed, Mar 7, 2018 at 10:31 AM, Darafei "Komяpa" Praliaskouski <
me at komzpa.net> wrote:

>
> As far as merging this in, are there objections to the function name
>> "postgis_compress_geometry" ? While the compression is actually happening
>> at the Postgres level, I think this name captures the net result of calling
>> the function, doesn't require the user to understand the internal mechanism
>> of compression, and suggests that use of the function alters the input data
>> and may affect performance.
>>
>
> compress_geometry will not kick in if column type is altered to EXTERNAL
> or PLAIN:
> https://www.postgresql.org/docs/10/static/storage-toast.html
>
> I would expect compress_geometry to change internal representation to some
> zigzag delta encoded thing, but not to zero out last bits.
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20180307/4e4150bc/attachment.html>