| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Wright, George" <George(dot)Wright(at)infimatic(dot)com> |
| Cc: | "John DeSoi" <desoi(at)pgedit(dot)com>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: plpgsql functions vs. embedded queries |
| Date: | 2008-09-29 23:07:11 |
| Message-ID: | 25540.1222729631@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
"Wright, George" <George(dot)Wright(at)infimatic(dot)com> writes:
>> Are funtions in plpgsql always slower than embedding sql queries in
>> string form in code like PHP?
> The functions took on average more than 10 times as long.
That suggests that you're getting a radically different, less efficient
plan for the "same" query inside a function. The exact reasons why are
hard to diagnose without a concrete example, but usually the story has
to do with comparing parameterized queries inside a function to
not-parameterized queries elsewhere. There are various workarounds
but the best choice depends on details you've not shown us.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shabala Deshpande | 2008-09-30 09:12:08 | !!! Compress individual tables with postgres |
| Previous Message | Wright, George | 2008-09-29 17:45:17 | Re: plpgsql functions vs. embedded queries |