| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "pavlicek(dot)david(at)gmail(dot)com" <pavlicek(dot)david(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18694: DISCARD ALL does not reset execution counters for plpgsql functions |
| Date: | 2024-11-07 13:38:07 |
| Message-ID: | CAKFQuwYU3NO2Tq8z_ZGou4+8KN8NKu86y1+m7LcyZFtLVwknZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-11-07 13:57:16 | Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' |
| Previous Message | PG Bug reporting form | 2024-11-07 10:02:01 | BUG #18696: Compatibility Query for Updating zlib1.dll in PostgreSQL 10.2 to Address Security Vulnerabilities |