Re: Bug or Feature - plpgsql odity

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 30 November 2003 08:15 pm, Tom Lane wrote:
> "Uwe C. Schroeder" <uwe(at)oss4u(dot)com> writes:
> > Is the %ROWTYPE" cached somewhere ? Is that intentional ?
>
> I see some fixes in the 7.4 CVS logs for dropped columns in plpgsql
> rowtypes. Not sure if they'd have any impact on added columns, but
> you could try. In general though I'd expect that plpgsql would cache
> the definitions of rowtypes, the same as it does for tables.
>
> regards, tom lane

So how would I force a reload of the cache ? I tried restarting postgres
alltogether, as well as recreating the procedure. Should I try a DROP and
CREATE cycle rather than a CREATE OR REPLACE ?
My understanding would be that the rowtype is compiled the moment the
procedure is created, so I'd expect a recreate of the procedure to take care
of the cache problem.

UC

- --
Open Source Solutions 4U, LLC 2570 Fleetwood Drive
Phone: +1 650 872 2425 San Bruno, CA 94066
Cell: +1 650 302 2405 United States
Fax: +1 650 872 2417
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/ysJjjqGXBvRToM4RAuq1AJ9LgkhYXEz19+0I8ou8/N7AeKPEgwCffzBT
XvJPiExWzZVyDAKjLUsbW4M=
=IQTs
-----END PGP SIGNATURE-----