Re: Using read_stream in index vacuum - Mailing list pgsql-hackers

From Kirill Reshke
Subject Re: Using read_stream in index vacuum
Date
Msg-id CALdSSPh82+TVme+R2paO_RAeU-zqZWFmjneQYoZLjDwaCbrfXw@mail.gmail.com
Whole thread Raw
In response to Re: Using read_stream in index vacuum  ("Andrey M. Borodin" <x4mmm@yandex-team.ru>)
List pgsql-hackers
Hi!

On Fri, 25 Oct 2024 at 17:01, Andrey M. Borodin <x4mmm@yandex-team.ru> wrote:
>
>
>
> > On 25 Oct 2024, at 00:55, Rahila Syed <rahilasyed90@gmail.com> wrote:
> >
> > While writing this email, I realized I evicted buffers for the table
> > and not the index. I will perform the test again. However,
> > I would like to know your opinion on whether this looks like
> > a valid test.
>
> Well, yes, kind of, you need drop caches from index. And, perhaps, you can have more indexes. You also can disable
autovaccumand just restart postgres instead of iterating through buffer caches.
 
>
> I've asked Thomas about performance implications and he told me that converting stuff to streamlined API is not
expectedto have better performance. It's needed to have decent perfromance when DIRECT_IO will be involved.
 
>
> Thanks!
>
>
> Best regards, Andrey Borodin.
>

I noticed CI failure for this patch. This does not look like a flap.

[0] https://cirrus-ci.com/task/4527545259917312
[1]
https://api.cirrus-ci.com/v1/artifact/task/4527545259917312/log/src/test/modules/test_misc/tmp_check/log/regress_log_007_vacuum_btree

-- 
Best regards,
Kirill Reshke



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: New "raw" COPY format
Next
From: Masahiko Sawada
Date:
Subject: Re: Count and log pages set all-frozen by vacuum