| From: | Craig Milhiser <craig(at)milhiser(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-09-23 00:52:20 |
| Message-ID: | CA+wnhO1zP13p5sn6d-top=-gmCnE+ymYEfkPbN2d=QKWMbp6Sg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Sep 22, 2024 at 11:02 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Craig Milhiser <craig(at)milhiser(dot)com> writes:
> > Has the referenced bug in this discussion[1] been released?
>
> I don't see any indication, either in that thread or in the commit
> log, that anything has been done in this area since about 16.2.
> It's not an easy problem in general.
>
> Having said that, Aurora is not Postgres, and I don't know
> how closely they track us. Can you reproduce this problem
> on a stock build of community Postgres?
>
> regards, tom lane
Thanks. I will work on setting that up. Also getting the aws team
involved.
The one query I investigated I rewrote. It took 15 seconds without parallel
to avoid this issue. I rewrote it and now the query completes in 0.2
seconds. For this query I can avoid the issue, at least temporarily, by
making a better query. But we need to solve the real problem. And I have
not looked at the other queries affecting me. I may not get so lucky
again.
I will post when I get the stock Postgres setup and running.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2024-09-23 01:46:07 | Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker |
| Previous Message | Tom Lane | 2024-09-22 16:56:00 | Re: BUG #18627: Regression (15 -> 16) - Join removal not performed when join condition spans multiple tables |