| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
| Subject: | Re: Allow to specify #columns in heap/index_form_tuple |
| Date: | 2017-03-31 17:48:27 |
| Message-ID: | CA+TgmoajkcPNRAh_AoP_GujxzEYBOPO9mbcKLe8HhhvjxiD1TQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 31, 2017 at 1:44 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> The covering indexes patch [1] really needs a version of
>> heap_form_tuple/index_form_tuple that allows to specify the number of
>> columns in the to-be generated tuple.
>
> I was thinking about that this morning, and wondering why exactly it
> would need such a thing. Certainly we're not going to store such a
> truncated tuple in the index, ...
The patch stores it in the index as a high key.
You might want to have a read through that patch. I think your
opinion would be helpful in determining how close that patch is to
being ready to commit (same for WARM).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-03-31 17:50:37 | Re: Allow to specify #columns in heap/index_form_tuple |
| Previous Message | Andres Freund | 2017-03-31 17:47:28 | Re: WIP: Covering + unique indexes. |