Re: Use streaming read I/O when enabling data checksums online

From: cca5507 <cca5507(at)qq(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Use streaming read I/O when enabling data checksums online
Date: 2026-06-04 02:43:47
Message-ID: tencent_1B56EC9443AD0BFD6AE35346657EF10C0E09@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > Attach a simple patch for $subject. I think we prefer streaming IO instead of
> > ReadBufferExtended(). Do I miss something?
>
> Thanks!  This code was written well before read streams existed, and recent
> work was focused on correctness of operation, that's the main reason it's using
> ReadBufferExtended still.  We probably want do something like this once the
> tree opens up after the v19 feature freeze.

Get it! I created a CF entry for this:

https://commitfest.postgresql.org/patch/6841/

--
Regards,
ChangAo Chen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2026-06-04 02:46:14 Re: Heads Up: cirrus-ci is shutting down June 1st
Previous Message Ewan Young 2026-06-04 02:32:45 Re: Use ereport() instead of elog() for invalid weights in setweight()