On Tue, 2015-07-14 at 16:19 -0400, Robert Haas wrote: > tuplesort.c does its own accounting, and TBH that seems like the right > thing to do here, too. The difficulty is, I think, that some > transition functions use an internal data type for the transition > state, which might not be a single palloc'd chunk. But since we can't > spill those aggregates to disk *anyway*, that doesn't really matter.
So would it be acceptable to just ignore the memory consumed by "internal", or come up with some heuristic? Regards, Jeff Davis -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers