Re: Useless memoize path generated for unique join on primary keys - Mailing list pgsql-performance

From Benjamin Coutu
Subject Re: Useless memoize path generated for unique join on primary keys
Date
Msg-id 052166fdb31e17b9ef89@zeyos.com
Whole thread Raw
In response to Re: Useless memoize path generated for unique join on primary keys  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Useless memoize path generated for unique join on primary keys
List pgsql-performance
> I'd say it's a pretty different problem. The cache hit ratio
> discussion on that thread talks about underestimating the hit ratio.
> That particular problem could only lead to Memoize plans *not* being
> chosen when they maybe should be. Not the other way around, which is
> your case.
>
> create statistics extdataregular_field_index_stats (ndistinct) on
> field, index from extdataregular;
> analyze extdataregular;
>
> would likely put that right.

Thanks David, using extended statistics for both (and only for both) tables solved this problem.

BTW, thank you for all your work on performance in recent releases.



pgsql-performance by date:

Previous
From: David Rowley
Date:
Subject: Re: Useless memoize path generated for unique join on primary keys
Next
From: David Rowley
Date:
Subject: Re: Useless memoize path generated for unique join on primary keys