On Thu, 28 Jul 2022 at 20:57, Peter Geoghegan <p...@bowt.ie> wrote: > > On Thu, Jul 28, 2022 at 6:56 AM Matthias van de Meent > <boekewurm+postg...@gmail.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.
Yes, my patch from 2020 was never reviewed, which is why I was resubmitting here. > I should be able to post something in a couple of weeks. How do you see that affecting this thread? -- Simon Riggs http://www.EnterpriseDB.com/