From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | iwebcas(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18514: Encountering an error invalid DSA memory alloc request size 1811939328 when executing script |
Date: | 2024-06-18 02:25:13 |
Message-ID: | CA+hUKGKXL5t-8KKQsOyAz7+eMRRAMkfbkFXwp4GLx0=nkF38dA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Jun 18, 2024 at 2:20 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Or enable_parallel_hash=off.
And if that allows the query to run, and it still uses the same basic
query plan with a Hash Right Join there, I wonder if it also uses a
huge number of batches, and if it does but manages to succeed, I
wonder if that could be just due to a difference in size of the
per-batch objects? I vaguely recall that there was a proposal to cap
nbatch appropriately for that allocation, but the cap would be
different for serial and parallel cases due to the element sizes.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2024-06-18 06:11:40 | Re: JIT crash introduced by 6185c9737c with LLVM 14 |
Previous Message | Thomas Munro | 2024-06-18 02:20:08 | Re: BUG #18514: Encountering an error invalid DSA memory alloc request size 1811939328 when executing script |