>
> > I'm not sure it is usefull in release notes since it is more about API,
> and not
> > user-facing change. Just in case.
> > GiST opclasses now can omit compress and decompress functions. If
> compress
> > function is omited, IndexOnlyScan is enabled for opclass without any
> extra
> > change.
> > https://github.com/postgres/postgres/commit/
> > d3a4f89d8a3e500bd7c0b7a8a8a5ce1b47859128
>
> Uh, we do have this for SP-GiST:
>
> Allow SP-GiST indexes to optionally use compression (Teodor Sigaev,
> Heikki Linnakangas, Alexander Korotkov, Nikita Glukhov)
>
> I am unclear how far downt the API stack I should go in documenting
> changes like this.
>
It is also a bit misleading - the idea in that change is that now index
representation can be a lossy version of actual data type (a box instead of
polygon as a referende, so a changelog entry can tell "Allow SP-GiST index
creation for polygon datatype."). There is no "decompression" for such
thing. "compression" sounds like gzip for me in user-facing context.