Re: DISCARD ALL does not force re-planning of plpgsql functions/procedures - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: DISCARD ALL does not force re-planning of plpgsql functions/procedures
Date
Msg-id CAGECzQT5W540ZHN28xX-Tcd_VMeO08SbkP_6bGgf8C+M+2L0CA@mail.gmail.com
Whole thread Raw
In response to Re: DISCARD ALL does not force re-planning of plpgsql functions/procedures  (Jelte Fennema-Nio <postgres@jeltef.nl>)
List pgsql-hackers


On Sun, May 26, 2024, 12:26 Jelte Fennema-Nio <postgres@jeltef.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. 

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: DISCARD ALL does not force re-planning of plpgsql functions/procedures
Next
From: Hannu Krosing
Date:
Subject: Re: DROP OWNED BY fails to clean out pg_init_privs grants