tag:blogger.com,1999:blog-8839574367290288724.post5582753029183314816..comments2023-12-11T13:13:11.330-08:00Comments on Pavel Stehule's blog: plpgsql_check can detect bad default volatility flagPavel Stěhulehttp://www.blogger.com/profile/01996484227228696817noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8839574367290288724.post-12369161324149645462018-11-28T21:26:50.626-08:002018-11-28T21:26:50.626-08:00It is not a problem with LATERAL JOIN - these quer...It is not a problem with LATERAL JOIN - these queries are prepared - look to README <a href="https://github.com/okbob/plpgsql_check#mass-check" rel="nofollow">https://github.com/okbob/plpgsql_check#mass-check</a><br /><br />SELECT p.proname, tgrelid::regclass, cf.*<br /> FROM pg_proc p<br /> JOIN pg_trigger t ON t.tgfoid = p.oid <br /> JOIN pg_language l ON p.prolang = l.oid<br /> JOIN pg_namespace n ON p.pronamespace = n.oid,<br /> LATERAL plpgsql_check_function(p.oid, t.tgrelid) cf<br /> WHERE n.nspname = 'public' and l.lanname = 'plpgsql'Pavel Stěhulehttps://www.blogger.com/profile/01996484227228696817noreply@blogger.comtag:blogger.com,1999:blog-8839574367290288724.post-73563242737203063432018-11-28T13:16:30.607-08:002018-11-28T13:16:30.607-08:00Good work, this is a nice performance boost!
Would...Good work, this is a nice performance boost!<br />Wouldn't it be cool if <b>select *</b> would output the function name too in a separate result column to write a more complex query to check all functions at once?Anonymousnoreply@blogger.com