Re: BUG #18694: DISCARD ALL does not reset execution counters for plpgsql functions

In my opinion it is a bug. Documentation clearly states that DISCARD ALL
"resets the session to its initial state", which is not true. So either
it's a documentation error and DISCARD ALL isn't meant to completely reset
the state, or it's meant to completely reset the state and then it's a bug
in its implementation (whether it is a missing feature or bug in existing
one). I agree that Implementing a new user-exposed command and then calling
it within DISCARD ALL is probably the right solution to the problem.

David P.

čt 7. 11. 2024 v 14:38 odesílatel David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> napsal:

> On Thursday, November 7, 2024, PG Bug reporting form <
> noreply(at)postgresql(dot)org> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 18694
>> Logged by: David Pavlíček
>> Email address: pavlicek(dot)david(at)gmail(dot)com
>> PostgreSQL version: 13.13
>> Operating system: Linux
>> Description:
>>
>> In my opinion, the DISCARD ALL command should reset the internal
>> execution counters of plpgsql functions.
>>
>>
> To my knowledge there is no user-exposed way to reset those counters.
> Thus discard all cannot reset them. It is a missing feature, not a bug.
> One that I agree makes sense to add.
>
> David J.
>
>