| From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
|---|---|
| To: | Erik Rijkers <er(at)xs4all(dot)nl> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: WIP: Covering + unique indexes. |
| Date: | 2018-04-05 14:07:57 |
| Message-ID: | CAPpHfdsx=V7mTH3GQ564_u=oiOk6Bo2gR0nMWo_dYqNf7Tyr_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 5, 2018 at 5:02 PM, Erik Rijkers <er(at)xs4all(dot)nl> wrote:
> On 2018-04-05 00:09, Alexander Korotkov wrote:
>
>> Thank you for review! Revised patchset is attached.
>> [0001-Covering-core-v12.patch]
>> [0002-Covering-btree-v12.patch]
>> [0003-Covering-amcheck-v12.patch]
>> [0004-Covering-natts-v12.patch]
>>
>
> Really nice performance gains.
>
> I read through the docs and made some changes. I hope it can count as
> improvement.
>
Thank you for your improvements of the docs. Your chenges will be
incorporated into new revision of patchset which I'm going to post today.
> It would probably also be a good idea to add the term "covering index"
> somewhere, at least in the documentation's index; the term does now not
> occur anywhere. (This doc-patch does not add it)
>
I'll think about it. May be we'll define "covering index" in the docs.
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2018-04-05 14:26:10 | Re: Flexible configuration for full-text search |
| Previous Message | Tom Lane | 2018-04-05 14:04:46 | Re: typcategory for regconfig |