Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: plpgsql functions vs. embedded queries
- From: John DeSoi <desoi(at)pgedit(dot)com>
- To: "Wright, George" <George(dot)Wright(at)infimatic(dot)com>
- Cc: <pgsql-novice(at)postgresql(dot)org>
- Subject: Re: plpgsql functions vs. embedded queries
- Date: Mon, 29 Sep 2008 13:15:33 -0400
- Message-id: <1A05FF7F-A5F6-43B2-89BF-AB6C7C2352F0@pgedit.com> <text/plain>
On Sep 29, 2008, at 9:50 AM, Wright, George wrote:
Are funtions in plpgsql always slower than embedding sql queries in string form in code like PHP? I ran several tests and they seemed to always perform that way. I would have thought the pre-planning would have made them faster. Would re-writing the functions C make them faster than the embedded queries?
I'd say no, they should not always be slower. Did you try preparing your PHP call to the function? Did you mark your function as STABLE if you are not modifying the database?
John DeSoi, Ph.D.
- Follow-Ups:
- Re: plpgsql functions vs. embedded queries
- From: Wright, George
- Re: plpgsql functions vs. embedded queries
- References:
- plpgsql functions vs. embedded queries
- From: Wright, George
- plpgsql functions vs. embedded queries
- Prev by Date: plpgsql functions vs. embedded queries
- Next by Date: Re: plpgsql functions vs. embedded queries
- Previous by thread: plpgsql functions vs. embedded queries
- Next by thread: Re: plpgsql functions vs. embedded queries
- Indexes: