Re: Streaming I/O, vectored I/O (WIP)

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Streaming I/O, vectored I/O (WIP)
Date: 2024-03-12 06:45:00
Message-ID: CA+hUKGJFJn3WeC+q3hNe_bpiLVKVSXpm2=wTBQMDpaRTNFmiCw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 12, 2024 at 7:40 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> possible. So in the current patch you say "hey please read these 16
> blocks" and it returns saying "only read 1", you call again with 15

Oops, typo worth correcting: s/15/16/. Point being that the caller is
interested in more blocks after the original 16, so it uses 16 again
when it calls back (because that's the size of the Buffer array it
provides).

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-03-12 06:52:01 Re: Add new error_action COPY ON_ERROR "log"
Previous Message Thomas Munro 2024-03-12 06:40:00 Re: Streaming I/O, vectored I/O (WIP)