Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker

From: Craig Milhiser <craig(at)milhiser(dot)com>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, 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-15 16:43:52
Message-ID: CA+wnhO1=yWXFSK7+rDWP7TzUbEFW9r8kHwASU3zFmqLYdOjJyQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I applied the patch for the parallel hash and ran that against my
production data. The query worked with parallel workers. That patch was
applied on top of the earlier patch for the invalid Susa memory alloc that
started this thread.

From my view as a user, these are both fixed and can be marked as such. We
will wait for the patches to role through the release cycles.

If you change the patch and need another test with real data please let me
know.

Thank you for your time and effort on these issues.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-10-15 17:51:15 Re: BUG #18656: "STABLE" function sometimes does not see changes
Previous Message PG Bug reporting form 2024-10-15 11:00:01 BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault