-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Le 6 août 08 à 20:42, Marko Kreen a écrit :
But you missed my point: if you don't have functions backed by table,
the DROP+CREATE results in inappropriate behaviour that can be
avoided.
Just wanted to say I agree with Marko here: it seems we have here a
pretty nice (and required) core feature which does not work all of the
time. It might be a difficult case to get right, but we certainly are
NOT getting it right now.
Whatever the workarounds, it would be nice that plan invalidation
worked whenever it makes sense, and DROP FUNCTION certainly makes
sense. Allowing REPLACE function to change return type (adding an OUT
parameter, the TABLE column list, etc) would certainly be a good
feature to add, but having existing feature set behave correctly is
more important.
It seems to qualify the complaint as a bug.
Regards,
- --
Dimitri Fontaine
PostgreSQL DBA, Architecte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkiaAPsACgkQlBXRlnbh1bl3CQCgvtP09HyFgzdqWVEpmGBA4bXy
3YUAoKLCrP+2AGqmctL9IBFmpUUmdssD
=b8HX
-----END PGP SIGNATURE-----
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
