Re: BUG #16089: Index only scan does not happen but expected

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: Stepan Yankevych <Stepan_Yankevych(at)epam(dot)com>
Cc: "stepya(at)ukr(dot)net" <stepya(at)ukr(dot)net>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16089: Index only scan does not happen but expected
Date: 2019-10-30 15:10:06
Message-ID: 20191030151006.cja5q3hd6fclwuq4@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On Wed, Oct 30, 2019 at 02:18:09PM +0000, Stepan Yankevych wrote:
>
> >> And in fact at least in my tests this was indeed faster
> Can you show execution plan when index is used?
> Does it uses Index only scan or index scan and table scan?

Yes, at the bottom of the plan there was an Index Only Scan going
through l1_snapshot_201811 (although while populating the table I've set
values only for not nullable columns).

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dmitry Dolgov 2019-10-30 15:14:39 Re: BUG #16089: Index only scan does not happen but expected
Previous Message PG Bug reporting form 2019-10-30 14:46:41 BUG #16090: Migración con pg_dump