Re: Loose indexscan and partial indexes

From: "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Loose indexscan and partial indexes
Date: 2017-02-10 14:04:32
Message-ID: 20170210140432.GB8667@hjp.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2017-02-10 14:24:36 +0100, Thomas Kellerer wrote:
> Peter J. Holzer schrieb am 10.02.2017 um 14:02:
> > So it's doing a sequential scan on the initial select in the recursive
> > CTE, but using the index on the subsequent selects.
> >
> > But why? If it uses the index on
> > SELECT MIN(periodizitaet) FROM facttable_imf_ifs WHERE periodizitaet > 'x'
> > shouldn't it be able to use the same index on
> > SELECT MIN(periodizitaet) FROM facttable_imf_ifs
>
> What is the definition of the index facttable_imf_ifs_periodizitaet_idx?

The solution to the puzzle was just 2 paragraphs further down.

Looks like I have to practice this arc of suspense thing ;-)

hp

--
_ | Peter J. Holzer | A coding theorist is someone who doesn't
|_|_) | | think Alice is crazy.
| | | hjp(at)hjp(dot)at | -- John Gordon
__/ | http://www.hjp.at/ | http://downlode.org/Etext/alicebob.html

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Roberto Balarezo 2017-02-10 15:17:02 Fwd: Query parameter types not recognized
Previous Message Rakesh Kumar 2017-02-10 13:45:04 Re: clarification about standby promotion