Re: Trouble with hashagg spill I/O pattern and costing
Jeff Davis <pgsql@j-davis.com>
From: Jeff Davis <pgsql@j-davis.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Date: 2020-05-21T19:04:19Z
Lists: pgsql-hackers
On Thu, 2020-05-21 at 20:54 +0200, Tomas Vondra wrote: > The last column is master with the tlist tweak alone - it's better > than > hashagg on master alone, but it's not nearly as good as with both > tlist > and prealloc patches. Right, I certainly think we should do the prealloc change, as well. I'm tweaking the patch to be a bit more flexible. I'm thinking we should start the preallocation list size ~8 and then double it up to ~128 (depending on your results). That would reduce the waste in case we have a large number of small partitions. Regards, Jeff Davis
Commits
-
Use CP_SMALL_TLIST for hash aggregate
- 4cad2534da6d 13.0 landed
-
Avoid fragmentation of logical tapes when writing concurrently.
- 896ddf9b3cd7 13.0 landed