Re: Prefetch the next tuple's memory during seqscans - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: Prefetch the next tuple's memory during seqscans
Date
Msg-id CAJ7c6TNh3HcEQ=BfbCf2DWTwLfyPiLqftAH2GW0MBaiSOwehgQ@mail.gmail.com
Whole thread Raw
In response to Prefetch the next tuple's memory during seqscans  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Prefetch the next tuple's memory during seqscans  (David Rowley <dgrowleyml@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: WIN32 pg_import_system_collations
Next
From: Michel Pelletier
Date:
Subject: Re: Proposal to use JSON for Postgres Parser format