Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: Parallel Seq Scan vs kernel read ahead
Date
Msg-id CA+TgmoZmqM2dji2+vhLZaRpruHs3Ojc0wTFa3Wj_Sm91-fw6=g@mail.gmail.com
Whole thread Raw
In response to Re: Parallel Seq Scan vs kernel read ahead  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Parallel Seq Scan vs kernel read ahead  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
Tree view 
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.

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

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Parallel Seq Scan vs kernel read ahead
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: password_encryption default