Re: Prefetch the next tuple's memory during seqscans

From: Aleksander Alekseev <aleksander(at)timescale(dot)com>
To: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Prefetch the next tuple's memory during seqscans
Date: 2022-10-31 14:12:22
Message-ID: CAJ7c6TNh3HcEQ=BfbCf2DWTwLfyPiLqftAH2GW0MBaiSOwehgQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi David,

> I'll add this to the November CF.

Thanks for the patch.

I wonder if we can be sure and/or check that there is no performance
degradation under different loads and different platforms...

Also I see 0001 and 0003 but no 0002. Just wanted to double check that
there is no patch missing.

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michel Pelletier 2022-10-31 14:55:25 Re: Proposal to use JSON for Postgres Parser format
Previous Message Peter Eisentraut 2022-10-31 14:09:36 Re: WIN32 pg_import_system_collations