pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: rbrooks <rbrooks@ctrlv.ca>
To: pgsql-hackers@postgresql.org
Subject: Re: enable_incremental_sort changes query behavior
Date: Mon, 1 Mar 2021 23:23:12 +0100
Message-ID: <b3878234-e550-9208-3510-5762f79487d2@enterprisedb.com> (raw)
In-Reply-To: <1614626597083-0.post@n3.nabble.com>
References: <20201029220652.glf4xk2p7wkfisb6@development>
	<CAAaqYe9P261NfjqhAkDbPGEjqf_8ZyayxTYUEdEnPOqmLRb6EA@mail.gmail.com>
	<20201030210316.cbwv4arwp4lcfgx2@development>
	<CAAaqYe_izhFTq1FLgUxa+J+_bY8FGBNiHjTj=EzrSA72tvacEw@mail.gmail.com>
	<20201103023743.sswkl6h74dkbcfmp@development>
	<20201103213942.sj3qohewdshrw4oz@development>
	<CAAaqYe8bEA_dqGm0XB=95VM7Fab+4xDvKdYA2YP65KsBQi6GAQ@mail.gmail.com>
	<87bfc0bb-34c3-b3fe-7674-0220055fabaa@postgrespro.ru>
	<CAJKUy5iMUVBpBnWyz9fhjw-gsM6yvSqb+vYGMyG5QfANvhhcLw@mail.gmail.com>
	<c9c81296-9212-d247-b28b-b7810ee0a907@enterprisedb.com>
	<1614626597083-0.post@n3.nabble.com>

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





view thread (61+ messages)  latest in thread

Message-ID: <b3878234-e550-9208-3510-5762f79487d2@enterprisedb.com>
Permalink:  ../b3878234-e550-9208-3510-5762f79487d2@enterprisedb.com/
Also on:    postgresql.org/message-id/b3878234-e550-9208-3510-5762f79487d2@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tomas.vondra@enterprisedb.com, rbrooks@ctrlv.ca
  Subject: Re: enable_incremental_sort changes query behavior
  In-Reply-To: <b3878234-e550-9208-3510-5762f79487d2@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox