Re: overhead of plpgsql functions over simple select - Mailing list pgsql-general

From Tom Lane
Subject Re: overhead of plpgsql functions over simple select
Date
Msg-id 18918.1224823582@sss.pgh.pa.us
Whole thread Raw
In response to Re: overhead of plpgsql functions over simple select  ("Pavel Stehule" <pavel.stehule@gmail.com>)
Responses Re: overhead of plpgsql functions over simple select  ("Pavel Stehule" <pavel.stehule@gmail.com>)
List pgsql-general
"Pavel Stehule" <pavel.stehule@gmail.com> writes:
> postgres=# create function simplefce(a int, b int) returns int as
> $$select $1 + $2$$ language sql immutable strict;
> CREATE FUNCTION
> postgres=# create function simplefce1(a int, b int) returns int as
> $$begin return a+b; end;$$ language plpgsql immutable strict;
> CREATE FUNCTION

That's a pretty unfair comparison, because that SQL function is simple
enough to be inlined.  The place to use plpgsql is when you need some
procedural logic; at which point a SQL function simply fails to provide
the required functionality.

            regards, tom lane

pgsql-general by date:

Previous
From: "Pavel Stehule"
Date:
Subject: Re: overhead of plpgsql functions over simple select
Next
From: "Pavel Stehule"
Date:
Subject: Re: overhead of plpgsql functions over simple select