Re: Mysteriously varying index scan costs

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Mysteriously varying index scan costs
Date: 2018-09-24 08:56:10
Message-ID: CABOikdMLmBGTqcjXd98KHEhZtL_GyEXB5M4m-EjzbF7-Y-hzfw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Sep 24, 2018 at 2:20 PM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:

>
>
> But how can it be that the first run has to touch 74917 blocks,
> while whe second run only needs to touch 1185?
>
>
The first index scan may have killed lots of index tuples.

Thanks,
Pavan

--
Pavan Deolasee http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Richard Nielsen 2018-09-24 09:24:08 pgAdmin v4: The application server could not be contacted.
Previous Message Laurenz Albe 2018-09-24 08:50:15 Mysteriously varying index scan costs