Re: Using read_stream in index vacuum

From: Andrei Borodin <x4mmm(at)yandex-team(dot)ru>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: Junwang Zhao <zhjwpku(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Using read_stream in index vacuum
Date: 2024-10-21 20:49:27
Message-ID: 80101729543767@fszgwlsuez7jpill.myt.yp-c.yandex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Melanie, thanks for your comments.<br /><br />21.10.2024, 22:34, "Melanie Plageman" &lt;melanieplageman(at)gmail(dot)com&gt;:<br /><blockquote><p></p><p>The whole point of the read stream callback provided by the caller is<br />that the logic to get the next block should be there</p></blockquote>We must get number of blocks after examining last block. But callback returning EOF might be called before. With current API we have to restart.<div><br /></div><div>Removing extension lock will not change this.</div><div><br /></div><div><br /></div><div>Best regards, Andrey Borodin.</div>

Attachment Content-Type Size
unknown_filename text/html 585 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2024-10-21 21:05:17 Re: Using read_stream in index vacuum
Previous Message Mark Hill 2024-10-21 20:12:28 RE: msvc directory missing in PostgreSQL 17.0