Re: plpgsql functions organisation - Mailing list pgsql-general

From Jeff Janes
Subject Re: plpgsql functions organisation
Date
Msg-id CAMkU=1xhm0JwfRGdg19JLPOwh52QDjKgCi1+RZMfeP9zz7oGrQ@mail.gmail.com
Whole thread Raw
In response to Re: plpgsql functions organisation  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: plpgsql functions organisation
Re: plpgsql functions organisation
List pgsql-general
On Sat, May 2, 2015 at 1:05 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 05/02/2015 10:12 AM, Melvin Davidson wrote:
AFAIK, you cannot "package" functions in  PostgreSQL, but it is possible to
call a function from within a function.

That being said, I would seriously look at how and why you are writing
your functions
as functions that call other functions are not very efficient.

I am not following. That is what packaging is about, separating out 'units of work' so they can be combined as needed. Part of that is using existing functions in new functions/classes. In fact in the Postgres source I see this in many places. Now it is entirely possible I missed a memo, so I am open to a more detailed explanation of the inefficiencies involved.

The Postgres source is written in C, not in plpgsql.  C has a good optimizing compiler and plpgsql doesn't.
 
Cheers,

Jeff

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: plpgsql functions organisation
Next
From: Bill Moran
Date:
Subject: Re: plpgsql functions organisation