Postgres Pro
Downloads
Home   >   mailing lists

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

From Gregory Stark (as CFM)
Subject Re: Prefetch the next tuple's memory during seqscans
Date
Msg-id CAM-w4HNDp+=i1gCMWRozE8qBNzDBS=jewqAn+Hen2mOUs5C0xg@mail.gmail.com
Whole thread Raw
In response to Re: 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
Tree view 
On Sun, 29 Jan 2023 at 21:24, David Rowley <dgrowleyml@gmail.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

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] Add `verify-system` sslmode to use system CA pool for server cert
Next
From: Alexander Lakhin
Date:
Subject: Re: SQL/JSON revisited