| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Lowering the ever-growing heap->pd_lower |
| Date: | 2021-05-18 19:33:30 |
| Message-ID: | CAH2-Wzn3Z4ag9CKpWxafZsLUWsBLHxrGh6vZ4K89OnKuOn_AFQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 18, 2021 at 12:29 PM Matthias van de Meent
<boekewurm+postgres(at)gmail(dot)com> wrote:
> PFA the updated version of this patch. Apart from adding line pointer
> truncation in PageRepairFragmentation (as in the earlier patches), I
> also altered PageTruncateLinePointerArray to clean up all trailing
> line pointers, even if it was the last item on the page.
Can you show a practical benefit to this patch, such as an improvement
in throughout or in efficiency for a given workload?
It was easy to see that having something was better than having
nothing at all. But things are of course different now that we have
PageTruncateLinePointerArray().
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2021-05-18 20:45:06 | pgbench test failing on 14beta1 on Debian/i386 |
| Previous Message | Matthias van de Meent | 2021-05-18 19:29:00 | Re: Lowering the ever-growing heap->pd_lower |