| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>, David Rowley <dgrowleyml(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: problems with making relfilenodes 56-bits |
| Date: | 2022-10-10 12:10:22 |
| Message-ID: | CA+TgmoZ1aJqjFpCM=3Peah=g3Oq=A=8nevcfL3ZeSa4HC7bskA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 10, 2022 at 5:16 AM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> I have also executed my original test after applying these patches on
> top of the 56 bit relfilenode patch. So earlier we saw the WAL size
> increased by 11% (66199.09375 kB to 73906.984375 kB) and after this
> patch now the WAL generated is 58179.2265625. That means in this
> particular example this patch is reducing the WAL size by 12% even
> with the 56 bit relfilenode patch.
That's a very promising result, but the question in my mind is how
much work would be required to bring this patch to a committable
state?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2022-10-10 12:24:34 | Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records |
| Previous Message | Alvaro Herrera | 2022-10-10 10:06:45 | Re: [BUG] Logical replica crash if there was an error in a function. |