Re: Why could different data in a table be processed with different performance?

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Vladimir Ryabtsev <greatvovan(at)gmail(dot)com>
Cc: f(dot)pardi(at)portavita(dot)eu, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Why could different data in a table be processed with different performance?
Date: 2018-09-25 02:38:52
Message-ID: 20180925023852.GX2471@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, Sep 24, 2018 at 05:59:12PM -0700, Vladimir Ryabtsev wrote:
> > This seems significant..it means the heap was probably written in
> backwards
> order relative to the IDs, and the OS readahead is ineffective when index
> scanning across a range of IDs.
> But again, why is it different for one range and another? It was reversed
> for both ranges.

I don't have an explaination for it.. but I'd be curious to know
pg_stats.correlation for the id column:

SELECT schemaname, tablename, attname, correlation FROM pg_stats WHERE tablename='articles' AND column='article_id' LIMIT 1;

Justin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Vladimir Ryabtsev 2018-09-25 03:40:28 Re: Why could different data in a table be processed with different performance?
Previous Message Vladimir Ryabtsev 2018-09-25 02:31:06 Re: Why could different data in a table be processed with different performance?