Re: Postgres 11 release notes

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
Cc: Darafei Praliaskouski <me(at)komzpa(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Postgres 11 release notes
Date: 2018-06-19 15:18:16
Message-ID: 8E8CF1F8-BCB2-4D86-A059-4BF5138F6D87@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

> On 19 Jun 2018, at 12:40, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> wrote:
>
> On Tue, Jun 19, 2018 at 12:15 PM Alexander Korotkov
> <a(dot)korotkov(at)postgrespro(dot)ru> wrote:
>> On Sat, Jun 16, 2018 at 3:57 PM Darafei "Komяpa" Praliaskouski
>> <me(at)komzpa(dot)net> wrote:
>>>>
>>>>> 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.
>>
>> +1 that current wording looks confusing. But I think we need to
>> highlight that we have general SP-GiST improvement, not just support
>> for particular datatype. So, I propose following wording: "Allow
>> SP-GiST to use lossy representation of leaf keys, and add SP-GiST
>> support for polygon type using that".
>
> Oh, I missed that we have separate release notes entry for polygons
> indexing. Then second part of sentence isn't needed, it should be
> just "Allow SP-GiST to use lossy representation of leaf keys". If no
> objections, I'm going to commit that altogether with fixes by
> Liudmila.

Speaking of typos, I think I spotted two more: s/features is/feature is/.
Fixed in the attached diff.

cheers ./daniel

Attachment Content-Type Size
relnotes11typo.diff application/octet-stream 941 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2018-06-19 15:37:06 Re: Postgres 11 release notes
Previous Message Tom Lane 2018-06-19 15:11:30 Re: row_to_json(), NULL values, and AS

Browse pgsql-www by date

  From Date Subject
Next Message Alexander Korotkov 2018-06-19 15:37:06 Re: Postgres 11 release notes
Previous Message Stephen Frost 2018-06-19 14:51:02 merak server off-line