pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: David Steele <david@pgmasters.net>
To: Anastasia Lubennikova <a.lubennikova@postgrespro.ru>
Cc: Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Anastasia Lubennikova <lubennikovaav@gmail.com>
Subject: Re: Re: WIP: Covering + unique indexes.
Date: Mon, 26 Mar 2018 09:42:08 -0400
Message-ID: <d237cf3d-a8a6-b031-aea4-ca9fc7fa093d@pgmasters.net> (raw )
In-Reply-To: <CAPpHfduZrxM81gQ5jRqL5+EMUAmfb8GXDgOz9tKGrFttFw4OPg@mail.gmail.com >
References: <56168952.4010101@postgrespro.ru >
<7FEB0867-F4F2-4F18-8AA9-7BAA0BB32868@yandex-team.ru >
<151654594496.23710.401435331419974842.pgcf@coridan.postgresql.org >
<1d2b6e12-9e1c-8df5-fdd6-4d20d3791b86@postgrespro.ru >
<CAEepm=2gh3nKi2u18i4r=TLhMyZf6guWSwmrHEcwm7dyJahnow@mail.gmail.com >
<b91d08de-db32-490d-6287-5c47b506767c@postgrespro.ru >
<CAEepm=07Lry2eH+ORvnGn=zTrSQCR0oVgz_0JNTQKUXdzaAszg@mail.gmail.com >
<78ca1586-647c-e159-ebf3-30957e270c66@postgrespro.ru >
<CAPpHfdvPv8BJVNygLrNkyQDUcyKFhsa25epr0m3cExzxmek8VA@mail.gmail.com >
<CAPpHfdsRDDQ4sqpb2+igiRok3r_EVZ0GJNC+nC98-gxW02MGaQ@mail.gmail.com >
<CAH2-WzkHH1E7MR08zMKpoHEp8g=0xoTNwCOLt8B_ETP4SeGi=A@mail.gmail.com >
<CAPpHfdvrn6S_2ArObKtEErB3_Z9+rqKzzKQfJ6jryCoKoc=peA@mail.gmail.com >
<CAH2-WzmNgNi8TtGqpgGQ2gku=Jwb6yXNcoQ1uy-jA2diyfTK6Q@mail.gmail.com >
<CAPpHfduZrxM81gQ5jRqL5+EMUAmfb8GXDgOz9tKGrFttFw4OPg@mail.gmail.com >
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@pgmasters.net
view thread (217+ messages) latest in thread
Message-ID: <d237cf3d-a8a6-b031-aea4-ca9fc7fa093d@pgmasters.net>
Permalink: ../d237cf3d-a8a6-b031-aea4-ca9fc7fa093d@pgmasters.net/
Also on: postgresql.org/message-id/d237cf3d-a8a6-b031-aea4-ca9fc7fa093d@pgmasters.net
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: david@pgmasters.net, a.lubennikova@postgrespro.ru, a.korotkov@postgrespro.ru, pg@bowt.ie, thomas.munro@enterprisedb.com, x4mmm@yandex-team.ru, pgsql-hackers@lists.postgresql.org, lubennikovaav@gmail.com
Subject: Re: Re: WIP: Covering + unique indexes.
In-Reply-To: <d237cf3d-a8a6-b031-aea4-ca9fc7fa093d@pgmasters.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox