Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Craig Milhiser <craig@milhiser.com>
Cc: Andrei Lepikhov <lepihov@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-bugs@lists.postgresql.org
Date: 2024-10-09T19:54:41Z
Lists: pgsql-bugs
On Thu, Oct 10, 2024 at 5:28 AM Craig Milhiser <craig@milhiser.com> wrote: > Then the machine ran out of disk space: ERROR: could not write to file "base/pgsql_tmp/pgsql_tmp4942.1.fileset/o1859485of2097152.p0.0": No space left on device For that, I have a patch in the queue to unlink temporary files incrementally: https://www.postgresql.org/message-id/flat/CA+hUKG+RGdvhAdVu5_LH3Ksee+kW-XkTP_nMxBL+Rmgp3Tjb_w@mail.gmail.com That's just treating a symptom, though. Things have already gone quite wrong if we're repeatedly repartitioning our way up to 2 million batches and only giving up there because of Andrei's patch. I wonder if there something could be wrong with Parallel Hash Right Join, which we see in your plan. That's new-ish, and I vaguely recall another case where that seemed to be on the scene in a plan with a high number of batches... hmm. Definitely keen to see a reproducer with synthetic data if you can come up with one...
Commits
-
Fix extreme skew detection in Parallel Hash Join.
- 98c7c7152d2d 18.0 landed
- 4ac5d33a8b08 17.1 landed
- 53edc948580f 16.5 landed
- 1831545ca186 15.9 landed
- 20d94899414a 14.14 landed
- 45329466fdc9 13.17 landed
- 4fa80a6d7d4b 12.21 landed