Discussion: PostgreSQL stored procedure
Ref: http://www.postgresonline.com/journal/index.php?/archives/15-Stored-Procedures-in-PostgreSQL.html

(work In Progress): 

 
Those who not in favor:

Why NOT use Stored Procedures*
* Views may be all you need.
* An object-relational mapper (ORM) can help write queries safely.
* Difficult to version control stored procedures.
* Software rollouts may require more db changes.
* Could slow software development process
 

http://www.postgresql.org/files/documentation/pdf/9.3/postgresql-9.3-A4.pdf

E.30.1. Overview

Broadly enhanced stored procedure support. The DO statement supports ad-hoc or “anonymous”code blocks. Functions can now be called using named parameters. PL/pgSQL is now installed by default, and PL/Perl and PL/Python have been enhanced in several ways, including support for Python3. page 2094

 
Triggers, which initializes an action by an SQL Data Management Language statement (DML), mostly by INSERT and UPDATE statement are fully supported. - See more at: http://www.w3resource.com/PostgreSQL/tutorial.php#sthash.lEfFrtnQ.dpuf
Triggers, which initializes an action by an SQL Data Management Language statement (DML), mostly by INSERT and UPDATE statement are fully supported. - See more at: http://www.w3resource.com/PostgreSQL/tutorial.php#sthash.lEfFrtnQ.dpuf
Triggers, which initializes an action by an SQL Data Management Language statement (DML), mostly by INSERT and UPDATE statement are fully supported. - See more at: http://www.w3resource.com/PostgreSQL/tutorial.php#sthash.lEfFrtnQ.dpuf
Triggers, which initializes an action by an SQL Data Management Language statement (DML), mostly by INSERT and UPDATE statement are fully supported. - See more at: http://www.w3resource.com/PostgreSQL/tutorial.php#sthash.lEfFrtnQ.dpuf