Horton

Re: enable_incremental_sort changes query behavior

Tomas Vondra <tomas.vondra@enterprisedb.com>

View thread View on postgr.es
From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: rbrooks <rbrooks@ctrlv.ca>, pgsql-hackers@postgresql.org
Date: 2021-03-01T22:23:12Z
Lists: pgsql-hackers 
On 3/1/21 8:23 PM, rbrooks wrote:
> Just a bump to see if there is a time frame for a fix on this.
> 
> Google Cloud doesn't yet support setting the *enable_incremental_sort * flag
> yet.
> Was able to temporarily resolve by running the following though:
> 
> ALTER DATABASE corpdb SET enable_incremental_sort TO OFF;
> 
> Hope this helps others until the core issue has been resolved.
> 

I don't follow - all fixes in this thread were committed - that's why 
it's marked like that in the CF app. And thus it should be in the recent 
13.2 release.

I don't know what version is currently supported by Google Cloud, maybe 
they haven't upgraded their PostgreSQL version yet.

regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. Disallow SRFs when considering sorts below Gather Merge

  2. Error out when Gather Merge input is not sorted

  3. Fix get_useful_pathkeys_for_relation for volatile expressions

  4. Guard against core dump from uninitialized subplan.