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