| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
| Cc: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Peter Geoghegan <pg(at)bowt(dot)ie>, 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: Re: WIP: Covering + unique indexes. |
| Date: | 2018-03-26 13:42:08 |
| Message-ID: | d237cf3d-a8a6-b031-aea4-ca9fc7fa093d@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/26/18 6:10 AM, Alexander Korotkov wrote:
>
> So, as I get you're proposing to introduce INDEX_ALT_TID_MASK flag
> which would indicate that we're storing something special in the t_tid
> offset. And that should help us not only for covering indexes, but also for
> further btree enhancements including suffix truncation. What exactly do
> you propose to store into t_tid offset when INDEX_ALT_TID_MASK flag
> is set? Is it number of attributes in this particular index tuple?
It appears that discussion and review of this patch is ongoing so it
should not be marked Ready for Committer. I have changed it to Waiting
on Author since there are several pending reviews and at least one bug.
Regards,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Hernandez | 2018-03-26 13:42:39 | Re: Proposal: http2 wire format |
| Previous Message | Michael Paquier | 2018-03-26 13:23:50 | Re: PQHost() undefined behavior if connecting string contains both host and hostaddr types |