út 7. 3. 2023 v 10:46 odesílatel David Rowley napsal:
> On Tue, 7 Mar 2023 at 22:09, Pavel Stehule
> wrote:
> > I can live with it. This is an analytical query and the performance is
> not too important for us. I was surprised that the performance was about
> 25% worse, and so the hit ratio was
On Tue, 7 Mar 2023 at 22:09, Pavel Stehule wrote:
> I can live with it. This is an analytical query and the performance is not
> too important for us. I was surprised that the performance was about 25%
> worse, and so the hit ratio was almost zero. I am thinking, but I am not sure
> if the
út 7. 3. 2023 v 9:58 odesílatel David Rowley napsal:
> /On Tue, 7 Mar 2023 at 21:09, Pavel Stehule
> wrote:
> >
> > po 6. 3. 2023 v 22:52 odesílatel David Rowley
> napsal:
> >> I wonder if the additional work_mem required for Memoize is just doing
> >> something like causing kernel page cache
/On Tue, 7 Mar 2023 at 21:09, Pavel Stehule wrote:
>
> po 6. 3. 2023 v 22:52 odesílatel David Rowley napsal:
>> I wonder if the additional work_mem required for Memoize is just doing
>> something like causing kernel page cache evictions and leading to
>> fewer buffers for
po 6. 3. 2023 v 22:52 odesílatel David Rowley napsal:
> On Mon, 6 Mar 2023 at 21:55, Pavel Stehule
> wrote:
> > default https://explain.depesz.com/s/fnBe
>
> It looks like the slowness is coming from the Bitmap Index scan and
> Bitmap heap scan rather than Memoize.
>
>-> Bitmap Heap
On Mon, 6 Mar 2023 at 21:55, Pavel Stehule wrote:
> default https://explain.depesz.com/s/fnBe
It looks like the slowness is coming from the Bitmap Index scan and
Bitmap heap scan rather than Memoize.
-> Bitmap Heap Scan on public.item i (cost=285.69..41952.12
rows=29021 width=16)
po 6. 3. 2023 v 9:16 odesílatel David Rowley napsal:
> On Mon, 6 Mar 2023 at 20:34, Pavel Stehule
> wrote:
> > In one query I can see very big overhead of memoize node - unfortunately
> with hits = 0
> >
> > The Estimate is almost very good. See details in attachment
>
> Are you able to share
On Mon, 6 Mar 2023 at 20:34, Pavel Stehule wrote:
> In one query I can see very big overhead of memoize node - unfortunately with
> hits = 0
>
> The Estimate is almost very good. See details in attachment
Are you able to share the version number for this?
Also, it would be good to see EXPLAIN
Hi
In one query I can see very big overhead of memoize node - unfortunately
with hits = 0
The Estimate is almost very good. See details in attachment
Regards
Pavel
slow
Description: Binary data
