| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | nageshdbaa(at)gmail(dot)com, 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 23:40:55 |
| Message-ID: | 1715740.1762731655@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Mon, Nov 10, 2025 at 4:23 AM PG Bug reporting form
> <noreply(at)postgresql(dot)org> wrote:
>> ERROR: could not attach to dynamic shared area
>> DETAIL: invalid dsa_handle
> ereport(ERROR,
> (errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE),
> errmsg("could not attach to dynamic shared area")));
> Where do we emit that DETAIL message?
I'd not picked up on that point, but you're right: we don't emit any
such DETAIL anywhere, not in current and not in 16.2 either. Must
be a locally-modified tree, or maybe just a copy-paste error in the
report?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kamil Monicz | 2025-11-10 03:21:20 | Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18 |
| Previous Message | Michael Paquier | 2025-11-09 22:36:09 | Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18 |