| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DISCARD ALL does not force re-planning of plpgsql functions/procedures |
| Date: | 2024-05-26 19:26:51 |
| Message-ID: | CAGECzQROQcYhFfehunv25CWjFrNBzn9fXmbw3kDDbKVp3O6tXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 26 May 2024 at 19:39, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Hm, should it be? That's hard-won knowledge, and I'm not sure there
> is a good reason to believe it's no longer applicable.
I think for DISCARD ALL it would probably make sense to forget this
knowledge . Since that is advertised as "reset the session to its initial
state". DISCARD PLANS should probably forget about it though indeed.
> Note that any change in behavior there would affect prepared
> statements in general, not only plpgsql.
DISCARD ALL already removes all prepared statements and thus their run
counts, so for prepared statements there would be no difference there.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2024-05-26 19:30:36 | Re: DISCARD ALL does not force re-planning of plpgsql functions/procedures |
| Previous Message | Tom Lane | 2024-05-26 17:39:30 | Re: DISCARD ALL does not force re-planning of plpgsql functions/procedures |