| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Arseniy Mukhin <arseniy(dot)mukhin(dot)dev(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Use streaming read I/O in BRIN vacuuming |
| Date: | 2025-08-31 17:49:23 |
| Message-ID: | 40C3C039-C781-4295-B4C3-F9F4F3E401EC@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
> On 31 Aug 2025, at 21:17, Arseniy Mukhin <arseniy(dot)mukhin(dot)dev(at)gmail(dot)com> wrote:
>
> PFA the patch that migrates BRIN vacuum to the read stream API.
The patch is nice and straightforward. Looks good to me.
Some notes that do not seem to me problem of this patch:
1. This comment is copied 7 times already across codebase.
"It is safe to use batchmode as block_range_read_stream_cb"
Maybe we can refactor comments and function names...
2. Somehow brin_vacuum_scan() avoid dance of getting RelationGetNumberOfBlocks() many times to be entirely sure everything is scanned. Unlike other index vacuums, see btvacuumscan() for example.
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2025-08-31 18:10:30 | Re: PG 18 relnotes and RC1 |
| Previous Message | Alvaro Herrera | 2025-08-31 17:43:17 | Re: Adding REPACK [concurrently] |