Re: pg_stat_statements stores WITH HOLD cursor query with literals

On Tue, Oct 27, 2026 at 05:03:21PM -0500, Sami Imseih wrote:
> So at least for these two contrib modules, preserving the current behavior
> would seem to require keeping the nesting decision decoupled from a single
> shared nesting_level.
>
> Those differences could perhaps be worked around, but each extension would
> still need to decide what the value means for its own purposes, so they may
> still need some form of queryDesc state.

And I doubt that it would fly far without a way to handle the
concurrent activity of more than one extension. FWIW, to me,
QueryDesc is a natural fit to track the nesting level, still my
previous sentence points out that we had better use a different memory
area for each definition we'd want to put on a query basis.

I am wondering if we don't have a bit more we could do for each
QueryDesc at extension level, like activity tracking or stuff in this
area.
--
Michael