navidrome/db/pglite/build/message_context_reset.diff

--- a/pg_main.c
+++ b/pg_main.c
@@ -28,7 +28,8 @@
 
 // globals
 
-#define MemoryContextResetAndDeleteChildren(...)
+// PG17 dropped this macro; the no-op stub leaked every message's parse/plan state.
+#define MemoryContextResetAndDeleteChildren(ctx) MemoryContextReset(ctx)
 // #define SpinLockInit(...)
fix(pglite): stop leaking every wire message's memory in the wasm module The PGlite fork stubs MemoryContextResetAndDeleteChildren, which PostgreSQL 17 removed, as an empty macro, so MessageContext was never reset and each statement leaked its parse and plan state (about 10 KB). On a real library the process grew to 15 GB during the first scan and the host swapped itself to a crawl. The new build maps the macro to MemoryContextReset (message_context_reset.diff); memory now stays flat across thousands of statements. Adds PGlite.MemorySize for measuring. 2026-09-04 21:38:21 -04:00			`--- a/pg_main.c`
			`+++ b/pg_main.c`
			`@@ -28,7 +28,8 @@`

			`// globals`

			`-#define MemoryContextResetAndDeleteChildren(...)`
			`+// PG17 dropped this macro; the no-op stub leaked every message's parse/plan state.`
			`+#define MemoryContextResetAndDeleteChildren(ctx) MemoryContextReset(ctx)`
			`// #define SpinLockInit(...)`