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

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:34:36
Message-ID: CAGECzQT5W540ZHN28xX-Tcd_VMeO08SbkP_6bGgf8C+M+2L0CA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, May 26, 2024, 12:26 Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:

> DISCARD PLANS should probably forget about it though indeed.
>

DISCARD PLANS should probably **not** forget about it

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2024-05-26 21:19:57 Re: DROP OWNED BY fails to clean out pg_init_privs grants
Previous Message Pavel Stehule 2024-05-26 19:30:36 Re: DISCARD ALL does not force re-planning of plpgsql functions/procedures