On Thu, Jul 6, 2023 at 12:56 AM Daniel Gustafsson wrote:
> Lukas: do you have an updated patch for this commitfest to address David's
> comments?
>
I have a draft - I should be able to post an updated patch in the next
days. Thanks for checking!
Thanks,
Lukas
--
Lukas Fittl
> On 7 Mar 2023, at 10:51, David Rowley wrote:
>
> On Sun, 5 Mar 2023 at 13:21, Lukas Fittl wrote:
>> Alternatively (or in addition) we could consider showing the "ndistinct"
>> value that is calculated in cost_memoize_rescan - since that's the most
>> significant contributor to the cache hit
On Sun, 5 Mar 2023 at 13:21, Lukas Fittl wrote:
> Alternatively (or in addition) we could consider showing the "ndistinct"
> value that is calculated in cost_memoize_rescan - since that's the most
> significant contributor to the cache hit ratio (and you can influence that
> directly by
Hi,
I was debugging a planner problem on Postgres 14.4 the other day - and the
involved "bad" plan was including Memoize - though I don't necessarily
think that Memoize is to blame (and this isn't any of the problems recently
fixed in Memoize costing).
However, what I noticed whilst trying
