Re: sequential scan result order vs performance - Mailing list pgsql-hackers

From Albe Laurenz
Subject Re: sequential scan result order vs performance
Date
Msg-id A737B7A37273E048B164557ADEF4A58B539720AF@ntex2010i.host.magwien.gv.at
Whole thread Raw
In response to Re: sequential scan result order vs performance  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
Jim Nasby wrote:
> On 10/30/16 9:12 AM, Tom Lane wrote:
>> I think there will be a lot of howls.  People expect that creating
>> a table by inserting a bunch of rows, and then reading back those
>> rows, will not change the order.  We already futzed with that guarantee
>> a bit with syncscans, but that only affects quite large tables --- and
>> even there, we were forced to provide a way to turn it off.
> 
> Leaving a 30% performance improvement on the floor because some people
> don't grok how sets work seems insane to me.

+1

Yours,
Laurenz Albe

pgsql-hackers by date:

Previous
From: amul sul
Date:
Subject: Re: Query regarding selectDumpableExtension()
Next
From: Gilles Darold
Date:
Subject: Re: Patch to implement pg_current_logfile() function