Re: Parallel Seq Scan vs kernel read ahead - Mailing list pgsql-hackers

From David Rowley
Subject Re: Parallel Seq Scan vs kernel read ahead
Date
Msg-id CAApHDvqk43QPahyUcgOV8xAYMJH+TXy5PLm1PLk9Ow7D0Q929g@mail.gmail.com
Whole thread Raw
In response to Re: Parallel Seq Scan vs kernel read ahead  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Parallel Seq Scan vs kernel read ahead
List pgsql-hackers
On Sat, 23 May 2020 at 06:31, Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Thu, May 21, 2020 at 6:28 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> > Right, I think it's safe.  I think you were probably right that
> > ramp-up isn't actually useful though, it's only the end of the scan
> > that requires special treatment so we don't get unfair allocation as
> > the work runs out, due to course grain.
>
> The ramp-up seems like it might be useful if the query involves a LIMIT.

That's true, but I think the intelligence there would need to go
beyond, "if there's a LIMIT clause, do ramp-up", as we might have
already fully ramped up well before the LIMIT is reached.

David



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: PostgresSQL 13.0 Beta 1 on Phoronix
Next
From: Victor Yegorov
Date:
Subject: Failure to create GiST on ltree column