Re: Parallel Seq Scan vs kernel read ahead

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel Seq Scan vs kernel read ahead
Date: 2020-06-22 21:52:21
Message-ID: CA+hUKGLcdJ_sBSLAsmb7kNz25cBE_gdvFRFxqn+=ZqpNwOPVZw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 19, 2020 at 2:10 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> Here's a patch which caps the maximum chunk size to 131072. If
> someone doubles the page size then that'll be 2GB instead of 1GB. I'm
> not personally worried about that.

I wonder how this interacts with the sync scan feature. It has a
conflicting goal...

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-06-22 22:15:27 Re: Backpatch b61d161c14 (Introduce vacuum errcontext ...)
Previous Message Andres Freund 2020-06-22 20:57:12 Re: Backpatch b61d161c14 (Introduce vacuum errcontext ...)