From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Baca Radim <rad(dot)baca(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Item compression in the Gist index |
Date: | 2022-05-02 13:00:07 |
Message-ID: | 009a454ccae7e6a399bb601479682b0ee07bd663.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2022-05-02 at 14:48 +0200, Baca Radim wrote:
> we are developing an extension for multidimensional data. We have
> created a Gist index that is heavily inspired by a cube extension. Right
> now we would like to add some item compression since data items in a
> node share a significant portion of a tuple prefix. However, I have no
> idea how to handle information stored on a node level in Gists'
> compression method. Is there any example? Unfortunately, the cube
> extension does not implement item compression.
> To be more specific we would like to store in the node a common prefix
> for all tuples in the node.
> Thanks for any advice,
Perhaps the PostGIS source will inspire you. They are compressing an
entry to its bounding box.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2022-05-02 13:02:41 | Re: Unfiltered server logs routing via a new elog hook or existing emit_log_hook bypassing log_min_message check |
Previous Message | Ashutosh Bapat | 2022-05-02 12:56:33 | Re: Progress report removal of temp files and temp relation files using ereport_startup_progress |