YourSoft wrote:
> When you call a pgsql stored procedure (with PreparedStatement), that
> calls an other stored procedure, and you recall the stored procedure
> after dropping and recreating second stored procedure, the calling will
> throw an exception with:
That's a known issue. The first time you call the procedure, it's
compiled and cached. The second time you call it, the cached plan is no
longer valid because the function it depends on has been dropped and
recreated.
The good news is that Tom Lane has added support for plan invalidation
for 8.3 branch, so this should be fixed in the next major release. Until
that, you can just disconnect and reconnect, which clears the
per-connection cache, and it should work.
BTW, this problem is not specific to JDBC, another mailing list would've
been more appropriate.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
