Re: Any risks in using FUNCTIONs (stored procedures) instead of raw sql queries?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Any risks in using FUNCTIONs (stored procedures) instead of raw sql queries?
Date: 2008-11-19 19:15:20
Message-ID: 1227122120.11755.27.camel@jd-laptop.pragmaticzealot.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2008-11-19 at 18:40 +0900, Craig Ringer wrote:
> Phoenix Kiula wrote:
>
> > I have googled but it looks like there's a whole variety of
> > information from 2003 (when PG must have been quite different) until
> > now--some people find stored functions slow for web based apps, others
> > find it is worth the maintenance.
>
> If your web servers are very close in network terms to your database
> server, issue mostly non-trivial queries, and are on a low latency link,
> it probably doesn't matter *that* much.

For one query no... for a dynamic website that uses 100 - 200 queries to
draw a page?

....

15ms * 200, 3000ms = 3 secs * 2 (both ways) = 6 seconds.

Joshua D. Drake

--

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message WireSpot 2008-11-19 19:42:33 Prepared statement already exists
Previous Message Tom Lane 2008-11-19 18:28:55 Re: tracking down a warning