Original article title is "plprofiler – Getting a Handy Tool for Profiling Your PL/pgSQL Code." What is the implication behind the title used here, "If you still write stored procedures in a Database, you may need a profiler"?
We reverted the title. Submitted title was "If you still write stored procedures in a Database, you may need a profiler", which broke the site guidelines.
Submitters: accounts that editorialize titles eventually lose submission privileges, so please remember that the guidelines ask you to "use the original title, unless it is misleading or linkbait; don't editorialize".
> Essentially all applications that are performance-sensitive use a stored-procedure interface to run application logic inside the DBMS and avoid the crippling overhead of back-and-forth communication between the application and the DBMS.
Also stored procedures are convenient for complex data processing, SQL is much more expressive and efficient for selecting, grouping, joining than something like java.
