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

From: Vladimir Ryabtsev <greatvovan(at)gmail(dot)com>
To: pryzby(at)telsasoft(dot)com
Cc: 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:31:06
Message-ID: CAMqTPqks=FTmxVCoQQfPa=7DxTe1V3eLnJZrXq0B+AgdrPzYWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> If it does an index scan, I think that will badly fail to keep the same
order of heap TIDs - it'll be inserting rows in ID order rather than in (I
guess) reverse ID order.
According to the plan, it's gonna be seq. scan with filter.

Vlad

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Justin Pryzby 2018-09-25 02:38:52 Re: Why could different data in a table be processed with different performance?
Previous Message Justin Pryzby 2018-09-25 02:19:54 Re: Why could different data in a table be processed with different performance?