Re: Leftover reference to replacement selection 1 run case

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Leftover reference to replacement selection 1 run case
Date: 2017-12-12 23:21:20
Message-ID: CA+Tgmoaz_33YvCVqUKzJStmY6D_+636+xNe9jgpg26tEUMKdUw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 8, 2017 at 6:41 PM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> While reviewing the parallel CREATE INDEX patch, I noticed that commit
> 8b304b8b omitted to remove a comment that it made obsolete.
>
> Attached patch removes the comment.

I had to think about this for a while. I could see that the comment
is now wrong, but initially I wasn't sure why we didn't care about the
optimization any more. Eventually I had a thought: it's now
impossible to end up with only one tape, because each tape now always
contains the output of one quicksort operation, and if we only did one
quicksort operation, it would have been an in-memory sort and there
would be no tapes anyway. Once we create a first tape, we've overrun
work_mem, so there will always be a second one.

Does that sound right?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-12-12 23:21:54 Re: PATCH: Exclude unlogged tables from base backups
Previous Message David Steele 2017-12-12 23:18:09 Re: PATCH: Exclude unlogged tables from base backups