From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Carlo Stonebanks <stonec(dot)register(at)sympatico(dot)ca>, kescobar(at)estudiantes(dot)uci(dot)cu, pgsql-general(at)postgresql(dot)org |
Subject: | Re: What language is faster, C or PL/PgSQL? |
Date: | 2013-02-05 05:06:27 |
Message-ID: | 20130205050627.GA31830@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Feb 4, 2013 at 08:33:02AM -0600, Merlin Moncure wrote:
> On Sat, Feb 2, 2013 at 11:36 AM, Carlo Stonebanks
> <stonec(dot)register(at)sympatico(dot)ca> wrote:
> > Here is an advantage Plpgsql has:
> > http://www.postgresql.org/docs/9.1/static/plpgsql-expressions.html
> >
> > I guess you can offset this by creating your own prepared statements in C.
> > Otherwise, I can’t think of how C could be slower. I would choose C for
> > functions that don’t have SQL statements in them – e.g. math and string
> > processing.
>
> For cases involving data processing (SPI calls), C can be slower
> because pl/pgsql has a lot of optimizations in it that can be very
> easy to miss. I don't suggest writing backend C functions at all
> unless you are trying to interface with a C library to access
> functionality currently not exposed in SQL.
How is PL/pgSQL faster than C? I thought we had optimized PL/pgSQL to
save parsed functions, but I don't see how that would help with queries,
which use SPI. Am I missing something?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Carlo Stonebanks | 2013-02-05 05:51:35 | Re: What language is faster, C or PL/PgSQL? |
Previous Message | Kirk Wythers | 2013-02-05 03:40:19 | Re: partial time stamp query |