On Fri, 21 Oct 2022 at 17:09, Maxim Orlov <orlo...@gmail.com> wrote: > Reviews and opinions are very welcome!
I'm wondering whether the safest way to handle this is by creating a new TAM called "heap64", so that all storage changes happens there. (Obviously there are still many other changes in core, but they are more easily fixed). That would reduce the code churn around "heap", allowing us to keep it stable while we move to the brave new world. Many current users see stability as one of the greatest strengths of Postgres, so while I very much support this move, I wonder if this gives us a way to have both stability and innovation at the same time? -- Simon Riggs http://www.EnterpriseDB.com/
