Re: CURRENT OF causes an error when IndexOnlyScan is used

From: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: CURRENT OF causes an error when IndexOnlyScan is used
Date: 2018-02-21 14:33:55
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

20.02.2018 12:52, Aleksander Alekseev:
> Hi Anastasia,
>> I'd like to propose the patch that fixes the issue.
>> We already have a way to return heaptuple from IndexOnlyScan,
>> but it was not applied to b-tree for some reason.
>> Attached patch solves the reported bug.
>> Moreover, it will come in handy for "index with included attributes" feature
>> [1],
>> where we can store long (and even TOASTed) attributes in indextuple.
>> [1]
> I believe the patch should include a test that tries to reproduce an
> issue it tries to fix.
> Also maybe this code that repeats 3 times can be moved to a separate
> procedure?

Good point. Updated version with test is attached.

Anastasia Lubennikova
Postgres Professional:
The Russian Postgres Company

Attachment Content-Type Size
return_heaptuple_in_btree_indexonlyscan_v2.patch text/x-patch 5.5 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-02-21 15:28:04 Off-cycle back-branch releases next week
Previous Message David Rowley 2018-02-21 11:58:31 Re: [HACKERS] Runtime Partition Pruning