Re: Organize working memory under per-PlanState context - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Organize working memory under per-PlanState context
Date
Msg-id d776d2de48e6f0e71b110913b24aab44326fee36.camel@j-davis.com
Whole thread Raw
In response to Re: Organize working memory under per-PlanState context  (Andrei Lepikhov <lepihov@gmail.com>)
Responses Re: Organize working memory under per-PlanState context
Re: Organize working memory under per-PlanState context
List pgsql-hackers
On Wed, 2025-08-20 at 09:22 +0200, Andrei Lepikhov wrote:
> I'm not sure I understand your reasoning clearly. How do you know
> that
> the current subtree will not be rescanned with the same parameter
> set?
> Building a hash table repeatedly may be pretty costly, no?

We can check the eflags for EXEC_FLAG_REWIND. That might not be the
only condition we need to check, but we should know at plan time
whether a subtree might be executed more than once.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: pg_get_sequence_data Shows Non-NULL last_value for Freshly Created Sequence
Next
From: Tom Lane
Date:
Subject: Re: pg_get_sequence_data Shows Non-NULL last_value for Freshly Created Sequence