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 CAApHDvrpLa5NEJp_RpPPnJbGJF90pM7kZizwjbABAqAW1C24Rw@mail.gmail.com
Whole thread Raw
In response to Re: Parallel Seq Scan vs kernel read ahead  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
On Wed, 15 Jul 2020 at 12:24, David Rowley <dgrowleyml@gmail.com> wrote:
> If we've not seen any performance regressions within 1 week, then I
> propose that we (pending final review) push this to allow wider
> testing. It seems we're early enough in the PG14 cycle that there's a
> large window of time for us to do something about any reported
> performance regressions that come in.

I did that final review which ended up in quite a few cosmetic changes.

Functionality-wise, it's basically that of the v2 patch with the
PARALLEL_SEQSCAN_MAX_CHUNK_SIZE set to 8192.

I mentioned that we might want to revisit giving users some influence
on the chunk size, but we'll only do so once we see some conclusive
evidence that it's worthwhile.

David



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: OpenSSL randomness seeding
Next
From: Andy Fan
Date:
Subject: Re: Difference for Binary format vs Text format for client-server communication