Re: Prefetch the next tuple's memory during seqscans

From: "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Prefetch the next tuple's memory during seqscans
Date: 2023-04-03 19:47:20
Message-ID: CAM-w4HNDp+=i1gCMWRozE8qBNzDBS=jewqAn+Hen2mOUs5C0xg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 29 Jan 2023 at 21:24, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
> I've moved this patch to the next CF. This patch has a dependency on
> what's being proposed in [1].

The referenced patch was committed March 19th but there's been no
comment here. Is this patch likely to go ahead this release or should
I move it forward again?

--
Gregory Stark
As Commitfest Manager

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2023-04-03 20:00:00 Re: SQL/JSON revisited
Previous Message Daniel Gustafsson 2023-04-03 19:40:42 Re: [PATCH] Add `verify-system` sslmode to use system CA pool for server cert