Ways to shoot yourself in the foot with Postgres
"2. Push all your application logic into Postgres functions and procedures"<p>Why are functions and procedures (an abstraction layer at db layer) considered harmful to performance when the same abstraction layer will be required at the application layer (introducing out of process overhead and possibly network traffic)? I don't agree with this advice. (Or I don't understand it.)