On Wed, 2008-04-16 at 11:09 -0400, Tom Lane wrote: > "Gavin M. Roy" <[EMAIL PROTECTED]> writes: > > In 8.3.0, I'm seeing some oddities with SQL functions which I thought were > > immune to the planner data restrictions of plpgsql functions and the sort. > > Without a specific example this discussion is pretty content-free, but > in general SQL functions face the same hazards of bad parameterized > plans as plpgsql functions do.
I think it would help if there was some way to prepare functions to allow them to be posted and understood more easily. These would help: * a name obfuscator, so people can post functions without revealing inner workings of their company and potentially lose intellectual property rights over code posted in that way * a pretty printer, so we can better understand them when we see 'em Without these, I think we need to realise that many people will never post their SQL at all. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
