> 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?
I reproduced the issue on v17. I downloaded the source tarball, built it, passed tests, put my production database, analyzed and ran the query. As you expected, the same issue occurred. I have opened the incident with the AWS team as well.
select version();
version --------------------------------------------------------------------------------------------------
PostgreSQL 17.0 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit
Since I have this saved for building, if you need logs or have an experiment, let me know. I tried to reproduce the issue with artificial data simply but the query completed. A different optimization plan was created since the data skew was very different.
I have workarounds of turning parallel execution off for the known queries and when possible rewriting the queries.
Thanks for the help.
Craig
