Re: DISCARD ALL does not force re-planning of plpgsql functions/procedures

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:30:36
Message-ID: CAFj8pRBC+j+_GJGmYPeQ8AYjUWjXLbGFii0K0GDrtCeQaEaVwA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

ne 26. 5. 2024 v 21:27 odesílatel Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
napsal:

> 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.
>

+1

Pavel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2024-05-26 19:34:36 Re: DISCARD ALL does not force re-planning of plpgsql functions/procedures
Previous Message Jelte Fennema-Nio 2024-05-26 19:26:51 Re: DISCARD ALL does not force re-planning of plpgsql functions/procedures