From: Andreas Wenk <a.wenk@netzmeister-st-pauli.de>
To: Andrew McMillan <andrew@morphoss.com>
Cc: "\"Rodrigo E. De\" León Plicet" <rdeleonp@gmail.com>
Cc: pgsql-php@postgresql.org
Subject: Re: pl/php for windows
Date: Sat, 07 Mar 2009 18:51:56 +0100
Message-ID: <49B2B43C.4090508@netzmeister-st-pauli.de> (raw)
In-Reply-To: <1235038888.22166.48.camel@happy.mcmillan.net.nz>
References: <873a98c60902180641u2320846bq4261bde13d59dd7a@mail.gmail.com>
<499CAA23.3050504@lightlink.com>
<1235005446.22166.31.camel@happy.mcmillan.net.nz>
<499CCC25.80200@lightlink.com>
<a55915760902182234t6e867236mc7be47459fd815ab@mail.gmail.com>
<1235038888.22166.48.camel@happy.mcmillan.net.nz>
Andrew McMillan schrieb:
> On Thu, 2009-02-19 at 01:34 -0500, Rodrigo E. De León Plicet wrote:
>> On Wed, Feb 18, 2009 at 10:04 PM, Bob McConnell <rmcconne@lightlink.com> wrote:
>>> (...) we have a company policy forbidding stored procedures (...)
>> Why would that be?
>>
>> Just curious...
>
> I can't speak for Bob, and they probably have different reasons, but
> personally I almost always only write stored procedures in SQL or
> PL/PgSQL, and I think very hard about it before deciding to do so, and
> try and be careful to design to a minimal functionality that can then be
> used in normal SQL.
>
> There can be memory effects from loading a large interpreter into a
> PostgreSQL client, which can cause pain if you have many connections,
> but mostly I don't trust the software versions to become wildly out of
> sync and multiply the installation & maintenance complexity.
>
> PostgreSQL also can have some problems planning queries containing
> functions.
Hi Andrew,
woooh .... sounds like giving the advice to reduce the usage of user
defined functions to a minimum. But in my opinion it should be a good
idea to move functionality to the database in case you work with a
Language like PHP. As I recognized it is a good idea to do so 'cause the
database is often faster than PHP.
I am speaking of PL/pgsql and SQL udf's.
Did I misunterstand you? Are there other experiences? In which cases is
the planner forced to have problems with statements containing udf's?
Cheers
Andy
>
> ... that said, I *have* written a set of functions in PL/PgSQL for
> parsing iCalendar RRULE + DTSTART into a SETOF TIMESTAMP. Just purely
> for giggles, of course :-)
>
> Cheers,
> Andrew.
>
> PS. In a past life I was responsible for maintaining an application
> written entirely in Oracle's PL/SQL. I don't ever want to repeat that,
> so that probably imposes a bias of sorts too!
>
> ------------------------------------------------------------------------
> andrew (AT) morphoss (DOT) com +64(272)DEBIAN
> You never hesitate to tackle the most difficult problems.
> ------------------------------------------------------------------------
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: a.wenk@netzmeister-st-pauli.de, andrew@morphoss.com, rdeleonp@gmail.com
Subject: Re: pl/php for windows
In-Reply-To: <49B2B43C.4090508@netzmeister-st-pauli.de>
References: <873a98c60902180641u2320846bq4261bde13d59dd7a@mail.gmail.com> <499CAA23.3050504@lightlink.com> <1235005446.22166.31.camel@happy.mcmillan.net.nz> <499CCC25.80200@lightlink.com> <a55915760902182234t6e867236mc7be47459fd815ab@mail.gmail.com> <1235038888.22166.48.camel@happy.mcmillan.net.nz> <49B2B43C.4090508@netzmeister-st-pauli.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox