Re: Vectored I/O in bulk_write.c

From: Noah Misch <noah(at)leadboat(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Vectored I/O in bulk_write.c
Date: 2024-07-06 22:46:47
Message-ID: 20240706224647.b4.nmisch@google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 09, 2024 at 04:51:52PM +1200, Thomas Munro wrote:
> Here's a rebase. I decided against committing this for v17 in the
> end. There's not much wrong with it AFAIK, except perhaps an
> unprincipled chopping up of writes with large io_combine_limit due to
> simplistic flow control, and I liked the idea of having a decent user
> of smgrwritev() in the tree, and it probably makes CREATE INDEX a bit
> faster, but... I'd like to try something more ambitious that
> streamifies this and also the "main" writeback paths.

I see this in the CF as Needs Review since 2024-03-10, but this 2024-04-09
message sounds like you were abandoning it. Are you still commissioning a
review of this thread's patches, or is the CF entry obsolete?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joseph Koshakow 2024-07-06 23:04:38 Re: Remove dependence on integer wrapping
Previous Message Jeremy Schneider 2024-07-06 20:37:06 Re: Built-in CTYPE provider