| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com> |
| Subject: | Re: WIP: Covering + unique indexes. |
| Date: | 2018-03-27 17:14:49 |
| Message-ID: | 44f81c8a-1c93-d8c6-d318-cc0c8dfeec91@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> b) I don't like an idea to limiting usage of that field if we can do not that.
> Future usage could use it, for example, for different compression technics or
> something else.Or even removing t_tid from inner tuples to save 2 bytes in IndexTupleData. Of
course, I remember about aligment, but it could be subject to change too in future.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2018-03-27 17:15:43 | Re: WIP: Covering + unique indexes. |
| Previous Message | Alvaro Herrera | 2018-03-27 17:07:47 | Re: Backend memory dump analysis |