Re: Patch: plan invalidation vs stored procedures
Joshua D. Drake <jd@commandprompt.com>
From: Joshua Drake <jd@commandprompt.com>
To: Gregory Stark <stark@enterprisedb.com>
Cc: "Hannu Krosing" <hannu@2ndQuadrant.com>, "Tom Lane" <tgl@sss.pgh.pa.us>, "Asko Oja" <ascoja@gmail.com>, "Pavel Stehule" <pavel.stehule@gmail.com>, "Dimitri Fontaine" <dfontaine@hi-media.com>, <pgsql-hackers@postgresql.org>, "Andrew Dunstan" <andrew@dunslane.net>, "David Fetter" <david@fetter.org>, "Martin Pihlak" <martin.pihlak@gmail.com>
Date: 2008-08-19T16:01:33Z
Lists: pgsql-hackers
On Tue, 19 Aug 2008 12:48:06 +0100 Gregory Stark <stark@enterprisedb.com> wrote: > "Hannu Krosing" <hannu@2ndQuadrant.com> writes: > > > Maybe there should be something in postgreSQL docs that warns users > > against using functions in any non-trivial circumstances, as > > functions are not expected to behave like the rest of postgreSQL > > features and there is not plan to fix that ? > > Now who's trolling :) Although I read his remark as sarcastic after reading the entire thread I have to say it may be a good idea to have the something in the docs about the limitation. I never think about it anymore because I am used to the behavior. I can see where and entity like skype who has I am sure thousands of procedures would have this as a constant irritant. Do I think it should be pushed back to 8.3.x; no. It is a feature. I don't consider the existing behavior a bug. I consider it a limitation and we don't back patch fixes for limitations. Sincerely, Joshua D. Drake -- The PostgreSQL Company since 1997: http://www.commandprompt.com/ PostgreSQL Community Conference: http://www.postgresqlconference.org/ United States PostgreSQL Association: http://www.postgresql.us/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate