Re: BUG #16104: Invalid DSA Memory Alloc Request in Parallel Hash
James Coleman <jtc331@gmail.com>
From: James Coleman <jtc331@gmail.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2019-11-11T14:14:43Z
Lists: pgsql-bugs
On Sun, Nov 10, 2019 at 4:09 PM Thomas Munro <thomas.munro@gmail.com> wrote: > > I think I see what's happening: we're running out of hash bits. > > > Buckets: 4194304 (originally 4194304) Batches: 32768 (originally 4096) Memory Usage: 344448kB > > Here it's using the lower 22 bits for the bucket number, and started > out using 12 bits for the batch (!), and increased that until it got > to 15 (!!). After using 22 bits for the bucket, there are only 10 > bits left, so all the tuples go into the lower 1024 batches. Do we have this kind of problem with hash aggregates also? I've noticed the temp disk usage pattern applies to both, and the buffers stats shows that being the case, but unfortunately the hash aggregate node doesn't report memory usage for its hash or buckets info. Given it's not a join, maybe we only need buckets and not batches, but I don't know this part of the code at all, so I'm just guessing to assume either way. James
Commits
-
Rotate instead of shifting hash join batch number.
- 5c0a132cf141 9.4.26 landed
- 893eaf0be8be 9.5.21 landed
- 15861deb65cd 9.6.17 landed
- 8e89bc6dfd3d 10.12 landed
- 9e551a14cb45 11.7 landed
- 8052aaf521e4 12.2 landed
- e69d64454778 13.0 landed