| From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Kirill Reshke <reshkekirill(at)gmail(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, 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: | 2025-03-21 21:54:50 |
| Message-ID: | CAAKRu_ZSz=MkPvsdnSxeUwGtkNV8c8iS91rrO_-KPdKTyG_9=w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 21, 2025 at 3:23 PM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> I've committed the btree and gist read stream users. I think we can
> come back to the test after feature freeze and make sure it is super
> solid.
I've now committed the spgist vacuum user as well. I'll mark the CF
entry as completed.
I wonder if we should do GIN?
> Looking at the spgist read stream user, I see you didn't convert
> spgprocesspending(). It seems like you could write a callback that
> uses the posting list and streamify this as well.
It's probably not worth it -- since we process the pending list for
each page of the index.
- Melanie
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2025-03-21 22:05:34 | Re: RFC: Additional Directory for Extensions |
| Previous Message | Daniel Gustafsson | 2025-03-21 21:52:38 | Re: acronym, glossary and other related matters in the docs |