| From: | Tomas Vondra <tomas(at)vondra(dot)me> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, nageshdbaa(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19105: Parallel Hash Join crash when work_mem is small |
| Date: | 2025-11-09 17:49:13 |
| Message-ID: | 2bf93857-aedb-4968-aacc-2add30bea365@vondra.me |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 11/9/25 16:47, Tom Lane wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
>> PostgreSQL version: 16.2
>
>> Server terminates with:
>
>> ERROR: could not attach to dynamic shared area
>> DETAIL: invalid dsa_handle
>
> I could not reproduce this problem with current sources
> (either master or v16 branch tip). 16.2 is pretty old,
> so maybe an update will fix it for you.
>
FWIW I couldn't reproduce it on 16.2 either, even after forcing it to
actually do parallel hash join (the posted instructions were not enough
to make that happen on my system).
Presumably there's some additional detail making it fail, but there are
too many options to guess. Maybe it's some kernel limit, something in
ubuntu 22.04, or something else.
It's interesting the report claims this happens only "when work_mem is
small". I wonder if that happens simply because the plan changes.
regards
--
Tomas Vondra
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2025-11-09 22:35:10 | Re: BUG #19105: Parallel Hash Join crash when work_mem is small |
| Previous Message | Tom Lane | 2025-11-09 15:53:56 | Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18 |