From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Craig Milhiser <craig(at)milhiser(dot)com> |
Cc: | Andrei Lepikhov <lepihov(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker |
Date: | 2024-10-09 19:54:41 |
Message-ID: | CA+hUKGJBDYOeDkLgOgS_PJcMSYbuS7UHMXJMKf3Va2En5DDZ5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Oct 10, 2024 at 5:28 AM Craig Milhiser <craig(at)milhiser(dot)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:
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...
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2024-10-09 21:00:01 | BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index |
Previous Message | Craig Milhiser | 2024-10-09 16:28:24 | Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker |