On Wed, 31 Aug 2022 at 22:39, David Rowley wrote:
> My current thoughts are that this is a very trivial patch and unless
> there's any objections I plan to push it soon.
Pushed.
David
On Fri, 26 Aug 2022 at 16:48, David Rowley wrote:
> 0003: Changes writetuple to tell it what it should do in regards to
> freeing and adjusting the memory accounting.
>
> Probably 0003 could be done differently. I'm certainly not set on the
> bool args. I understand that I'm never calling it with
Hi,
Since doing some work for PG15 for speeding up sorts, I've been a
little irritated by the fact that dumptuples() calls WRITETUP, (which
is now always calling writetuple()) and calls pfree() on the tuple
only for dumptuples() to do
MemoryContextReset(state->base.tuplecontext) directly afterward
