| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Maximize page freezing |
| Date: | 2022-07-28 19:57:14 |
| Message-ID: | CAH2-WzmiuJEHVS-7mAJXRVqJLqMBHoGLUg3=RZ60kXNXUaDDdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 28, 2022 at 6:56 AM Matthias van de Meent
<boekewurm+postgres(at)gmail(dot)com> wrote:
> Great idea, yet this patch seems to only freeze those tuples that are
> located after the first to-be-frozen tuple. It should probably
> re-visit earlier live tuples to potentially freeze those as well.
I have a big patch set pending that does this (which I dubbed
"page-level freezing"), plus a bunch of other things that control the
overhead. Although the basic idea of freezing all of the tuples on a
page together appears in earlier patching that were posted. These were
things that didn't make it into Postgres 15.
I should be able to post something in a couple of weeks.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2022-07-28 20:05:37 | Re: PROXY protocol support |
| Previous Message | Robert Haas | 2022-07-28 19:09:32 | Re: pg_auth_members.grantor is bunk |