From: Tom Lane <tgl@sss.pgh.pa.us>
To: hysong0101@163.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18574: procedure cache does not invalidate when output parameter type mismatch
Date: Wed, 07 Aug 2024 12:55:47 -0400
Message-ID: <2051174.1723049747@sss.pgh.pa.us> (raw)
In-Reply-To: <18574-2ce7ba3249221389@postgresql.org>
References: <18574-2ce7ba3249221389@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> The reproduced script is as above. There is one out parameter in the two
> procedures. In the initial state, we make their types do not match and call
> the fisrt procedure which internally calls the other procedure. Then we will
> get "procedure parameter "r1" is an output parameter but corresponding
> argument is not writable". After this, we drop procedure + create procedure
> for p2. In this time, we re-call the fisrt procedure，we will get "cache
> lookup failed for function".
Fixed, thanks for the report!
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, hysong0101@163.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18574: procedure cache does not invalidate when output parameter type mismatch
In-Reply-To: <2051174.1723049747@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox