Re: Mysteriously varying index scan costs - Mailing list pgsql-general

From Pavan Deolasee
Subject Re: Mysteriously varying index scan costs
Date
Msg-id CABOikdMLmBGTqcjXd98KHEhZtL_GyEXB5M4m-EjzbF7-Y-hzfw@mail.gmail.com
Whole thread Raw
In response to Mysteriously varying index scan costs  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Mysteriously varying index scan costs  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-general


On Mon, Sep 24, 2018 at 2:20 PM, Laurenz Albe <laurenz.albe@cybertec.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

pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Mysteriously varying index scan costs
Next
From: Richard Nielsen
Date:
Subject: pgAdmin v4: The application server could not be contacted.