Re: Planner misestimation for JOIN with VARCHAR

On Wed, 10 Jun 2020 at 07:31, Michael Lewis <mlewis@entrata.com> wrote:
>
> On Tue, Jun 9, 2020 at 12:34 PM Sebastian Dressler <sebastian@swarm64.com> wrote:
>>
>> - Add an index on top of the whole PK
>> - Add indexes onto other columns trying to help the JOIN
>> - Add additional statistics on two related columns
>>
>> Another idea I had was to make use of generated columns and hash the PKs together to an BIGINT and solely use this
forthe JOIN. However, this would not work when not all columns of the PK are used for the JOIN.
 
>
>
> Can you expand on the additional statistics you created? Why was it on only two columns? Did you include MCVs type of
extendedstats?
 

Unfortunately, the join selectivity functions have yet to learn about
extended statistics.

David