On Sun, Sep 22, 2024 at 11:02 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Craig Milhiser <craig@milhiser.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.
