Re: Prefetch the next tuple's memory during seqscans

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, "Gregory Stark (as CFM)" <stark(dot)cfm(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: 2024-01-20 03:35:15
Message-ID: CALDaNm1AuGa5F9txX8RR21iVW8zEn-Bo7otxAXP1UXptmsB8MA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 10 Jul 2023 at 15:04, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> > On 10 Jul 2023, at 11:32, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> >
> >> On 4 Apr 2023, at 06:50, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> >
> >> Updated patches attached.
> >
> > This patch is marked Waiting on Author, but from the thread it seems Needs
> > Review is more apt. I've changed status and also attached a new version of the
> > patch as the posted v1 no longer applied due to changes in formatting for Perl
> > code.
>
> ..and again with both patches attached. Doh.

I'm seeing that there has been no activity in this thread for more
than 6 months, I'm planning to close this in the current commitfest
unless someone is planning to take it forward.

Regards,
Vignesh

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yongtao Huang 2024-01-20 04:08:52 Re: Optimize duplicate code and fix memory leak in function fetch_remote_table_info()
Previous Message vignesh C 2024-01-20 03:33:47 Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?