Re: cost_sort() may need to be updated - Mailing list pgsql-hackers

From Tom Lane
Subject Re: cost_sort() may need to be updated
Date
Msg-id 26210.1473609682@sss.pgh.pa.us
Whole thread Raw
In response to cost_sort() may need to be updated  (Peter Geoghegan <pg@heroku.com>)
Responses Re: cost_sort() may need to be updated  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
Peter Geoghegan <pg@heroku.com> writes:
> I think that we *can* refine this guess, and should, because random
> I/O is really quite unlikely to be a large cost these days (I/O in
> general often isn't a large cost, actually). More fundamentally, I
> think it's a problem that cost_sort() thinks that external sorts are
> far more expensive than internal sorts in general. There is good
> reason to think that that does not reflect the reality. I think we can
> expect external sorts to be *faster* than internal sorts with
> increasing regularity in Postgres 10.

TBH, if that's true, haven't you broken something?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Parallel tuplesort (for parallel B-Tree index creation)
Next
From: Peter Geoghegan
Date:
Subject: Re: cost_sort() may need to be updated