| From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PoC] Improve dead tuple storage for lazy vacuum |
| Date: | 2022-09-22 14:37:58 |
| Message-ID: | CAFBsxsHJYi8Q1EuSg=QV+ZGb08ej25XQA7jAcG49bJTqKhrrbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 22, 2022 at 7:52 PM John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
wrote:
>
>
> On Thu, Sep 22, 2022 at 1:26 PM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
wrote:
> > Good point. While keeping the chunks in the small nodes in sorted
> > order is useful for visiting all keys in sorted order, additional
> > branches and memmove calls could be slow.
>
> Right, the ordering is a property that some users will need, so best to
keep it. Although the node128 doesn't have that property -- too slow to do
so, I think.
Nevermind, I must have been mixing up keys and values there...
--
John Naylor
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-09-22 14:49:54 | Re: [RFC] building postgres with meson - v13 |
| Previous Message | Alvaro Herrera | 2022-09-22 14:15:50 | Re: Pruning never visible changes |