From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kenneth Marshall <ktm@rice.edu>
cc: pgsql-performance@lists.postgresql.org
Subject: Re: PostgreSQL 12.3 slow index scan chosen
In-reply-to: <20200619212338.GM1497@aart.rice.edu>
References: <20200619194914.GI1497@aart.rice.edu>
 <1755412.1592597470@sss.pgh.pa.us> <20200619204950.GL1497@aart.rice.edu>
 <1757512.1592600355@sss.pgh.pa.us> <20200619212338.GM1497@aart.rice.edu>
Comments: In-reply-to Kenneth Marshall <ktm@rice.edu>
	message dated "Fri, 19 Jun 2020 16:23:38 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1759983.1592604634.1@sss.pgh.pa.us>
Date: Fri, 19 Jun 2020 18:10:34 -0400
Message-ID: <1759984.1592604634@sss.pgh.pa.us>
Precedence: bulk

Kenneth Marshall <ktm@rice.edu> writes:
> On Fri, Jun 19, 2020 at 04:59:15PM -0400, Tom Lane wrote:
>> What's the actual maximum value of objectcustomfieldvalues.objectid,
>> and how does that compare to the endpoint value in the pg_stats
>> histogram for that column?  If you've got one outlier in the table,
>> it might get missed by ANALYZE.

> max(objectcustomfieldvalues.objectid) = 28108423 and here is the
> histogram for that column:

 ... 3304313,3693956,27667772}

Hmm, does seem like you have some outlier keys.  Are any of the keys in
the column you're trying to join to larger than 27667772?

			regards, tom lane