> On 20 May 2025, at 11:56, Daniel Gustafsson <dan...@yesql.se> wrote: > >> On 20 May 2025, at 04:29, Tom Lane <t...@sss.pgh.pa.us> wrote: > >> I want to argue for reverting, at least for v18. I do not think that >> ProcessGetMemoryContextInterrupt is anywhere near release-quality. >> I found out while poking into Valgrind leak reports that it leaks >> memory --- and does so in TopMemoryContext. > > Ugh, that's indeed a showstopper. Attached is a revert of the feature, I want > to re-read and re-test before pushing to make sure I didn't miss anything but > can go ahead with it later today.
This has now been done. -- Daniel Gustafsson
