Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1gn6Ir-0004bV-6h
	for pgsql-performance@arkaria.postgresql.org; Fri, 25 Jan 2019 18:34:09 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1gn6Ip-000316-St
	for pgsql-performance@arkaria.postgresql.org; Fri, 25 Jan 2019 18:34:07 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1gn6Ip-00030y-Ie
	for pgsql-performance@lists.postgresql.org; Fri, 25 Jan 2019 18:34:07 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1gn6In-0000b6-BH
	for pgsql-performance@postgresql.org; Fri, 25 Jan 2019 18:34:06 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x0PIY1d2003631;
	Fri, 25 Jan 2019 13:34:02 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "ldh@laurent-hasson.com" <ldh@laurent-hasson.com>
cc: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Zero throughput on a query on a very large table.
In-reply-to: 
 <BN6PR15MB1185AA2A1C14BBF83AE9C69B859B0@BN6PR15MB1185.namprd15.prod.outlook.com>
References: 
 <BN6PR15MB1185DB9366CD57353DDD22C4859B0@BN6PR15MB1185.namprd15.prod.outlook.com>,<29285.1548397485@sss.pgh.pa.us>
 <BN6PR15MB11858B89B18A47FAB8430A34859B0@BN6PR15MB1185.namprd15.prod.outlook.com>,<2201.1548439855@sss.pgh.pa.us>
 <BN6PR15MB1185AA2A1C14BBF83AE9C69B859B0@BN6PR15MB1185.namprd15.prod.outlook.com>
Comments: In-reply-to "ldh@laurent-hasson.com" <ldh@laurent-hasson.com>
	message dated "Fri, 25 Jan 2019 18:29:12 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3629.1548441241.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 Jan 2019 13:34:01 -0500
Message-ID: <3630.1548441241@sss.pgh.pa.us>
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Precedence: bulk

"ldh@laurent-hasson.com" <ldh@laurent-hasson.com> writes:
> Also, the original statement i implemented did not have all of that. Thi=
s is the normalized SQL that Postgres now gives when looking at the indice=
s.

[ squint... ]  What do you mean exactly by "Postgres gives that"?
I don't see any redundant COLLATE clauses in e.g. psql \d.

			regards, tom lane