From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Postgres 11 release notes |
Date: | 2018-05-18 13:53:02 |
Message-ID: | 20180518135302.GE3088@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
On Fri, May 18, 2018 at 10:56:25AM +0500, Andrey Borodin wrote:
> H, Bruce!
>
>
> 11 мая 2018 г., в 20:08, Bruce Momjian <bruce(at)momjian(dot)us> написал(а):
>
> I expect a torrent of feedback. ;-)
>
>
> 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.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2018-05-18 14:02:47 | Re: pg_control read error message |
Previous Message | Bruce Momjian | 2018-05-18 13:30:22 | Re: SCRAM with channel binding downgrade attack |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-05-18 14:28:12 | Re: Postgres 11 release notes |
Previous Message | Bruce Momjian | 2018-05-18 13:30:22 | Re: SCRAM with channel binding downgrade attack |