Re: Memory leak from ExecutorState context?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Melanie Plageman <melanieplageman@gmail.com>,
Jehan-Guillaume de Rorthais <jgdr@dalibo.com>,
pgsql-hackers@lists.postgresql.org,
Konstantin Knizhnik <knizhnik@garret.ru>,
Thomas Munro <thomas.munro@gmail.com>
Date: 2023-05-19T15:28:25Z
Lists: pgsql-hackers
Tomas Vondra <tomas.vondra@enterprisedb.com> writes: > I didn't push 0001, I don't think generally do separate pgindent patches > like this (I only run pgindent on large patches to ensure it doesn't > cause massive breakage, not separately like this, but YMMV). It's especially pointless when the main pgindent run for v16 is going to happen today (as soon as I get done clearing out my other queue items). regards, tom lane
Commits
-
Describe hash join implementation
- 507615fc533b 16.0 landed