Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1lGq4D-0006LO-Sd
	for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Mar 2021 21:27:01 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1lGq4C-0003Lf-PG
	for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Mar 2021 21:27:00 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <rbrooks@ctrlv.ca>)
	id 1lGo8W-0001o0-Ey
	for pgsql-hackers@lists.postgresql.org; Mon, 01 Mar 2021 19:23:20 +0000
Received: from n3.nabble.com ([162.255.23.22])
	by makus.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <rbrooks@ctrlv.ca>)
	id 1lGo8U-0005sx-68
	for pgsql-hackers@postgresql.org; Mon, 01 Mar 2021 19:23:19 +0000
Received: from n3.nabble.com (localhost [127.0.0.1])
	by n3.nabble.com (Postfix) with ESMTP id 14D6224AE2EF2
	for <pgsql-hackers@postgresql.org>; Mon,  1 Mar 2021 12:23:17 -0700 (MST)
Date: Mon, 1 Mar 2021 12:23:17 -0700 (MST)
From: rbrooks <rbrooks@ctrlv.ca>
To: pgsql-hackers@postgresql.org
Message-ID: <1614626597083-0.post@n3.nabble.com>
In-Reply-To: <c9c81296-9212-d247-b28b-b7810ee0a907@enterprisedb.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>
Subject: Re: enable_incremental_sort changes query behavior
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

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.





--
Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html