From: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
---|---|
To: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: CURRENT OF causes an error when IndexOnlyScan is used |
Date: | 2018-02-20 09:52:53 |
Message-ID: | 20180220095252.GA18315@e733.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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] https://commitfest.postgresql.org/17/1350/
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?
--
Best regards,
Aleksander Alekseev
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2018-02-20 10:06:26 | Re: pgbench - allow to specify scale as a size |
Previous Message | Amit Langote | 2018-02-20 09:24:24 | Re: unique indexes on partitioned tables |