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

From David Rowley
Subject Re: Prefetch the next tuple's memory during seqscans
Date
Msg-id CAApHDvrtOULaRJ=1DR3bRjUgC_U-iTg7xj2kFhcx614gWiHu4A@mail.gmail.com
Whole thread Raw
In response to Re: Prefetch the next tuple's memory during seqscans  (vignesh C <vignesh21@gmail.com>)
Responses Re: Prefetch the next tuple's memory during seqscans
List pgsql-hackers
On Wed, 4 Jan 2023 at 23:06, vignesh C <vignesh21@gmail.com> wrote:
> patching file src/backend/access/heap/heapam.c
> Hunk #1 FAILED at 451.
> 1 out of 6 hunks FAILED -- saving rejects to file
> src/backend/access/heap/heapam.c.rej

I've moved this patch to the next CF.  This patch has a dependency on
what's being proposed in [1]. I'd rather wait until that goes in
before rebasing this. Having this go in first will just make Melanie's
job harder on her heapam.c refactoring work.

David

[1] https://commitfest.postgresql.org/41/3987/



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: lockup in parallel hash join on dikkop (freebsd 14.0-current)
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Time delayed LR (WAS Re: logical replication restrictions)