| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | 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-02-27 04:02:48 |
| Message-ID: | CA+TgmoYtHb1+nOAFx7dmPtr6z+DnJODdS3icCoUfhHJ+BqozzA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 27, 2024 at 9:25 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Here's the 2 step version. The streaming_read.c API is unchanged, but
> the bugmfr.c API now has only the following extra functions:
>
> bool StartReadBuffers(..., int *nblocks, ..., ReadBuffersOperation *op)
> WaitReadBuffers(ReadBuffersOperation *op)
I wonder if there are semi-standard names that people use for this
kind of API. Somehow I like "start" and "finish" or "start" and
"complete" better than "start" and "wait". But I don't really know
what's best. If there's a usual practice, it'd be good to adhere to
it.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2024-02-27 04:08:31 | The const expression evaluation routine should always return a copy |
| Previous Message | Thomas Munro | 2024-02-27 03:54:36 | Re: Streaming I/O, vectored I/O (WIP) |