Re: Writing most code in Stored Procedures - Mailing list pgsql-general

From Ron Johnson
Subject Re: Writing most code in Stored Procedures
Date
Msg-id 46C71E63.4050903@cox.net
Whole thread Raw
In response to Re: Writing most code in Stored Procedures  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Writing most code in Stored Procedures  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Writing most code in Stored Procedures  (Guy Rouillier <guyr-ml1@burntmail.com>)
List pgsql-general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/18/07 11:08, Joshua D. Drake wrote:
> Josh Tolley wrote:
>> On 8/18/07, Ron Johnson <ron.l.johnson@cox.net> wrote:
>>> Interesting.  Does PG have to initiate the Perl interpreter every
>>> time you call a Perl-written SP?
>> IIRC PostgreSQL should only load the perl interpreter once per session.
>
> Right.

I'd have been stunned if you did it any other way.

So why is Perl-SP-INSERT so much slower than Perl-SQL-INSERT?

(I can imagine that the SP code path would be longer, but since IO
is the slowest part of the system, I'm surprised that it's *that*
much slower.)

- --
Ron Johnson, Jr.
Jefferson LA  USA

Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGxx5jS9HxQb37XmcRAn1vAKCEWTovgcj/w/uFVK0nankGdbOFuACg6HSq
dUnMN0dPsdQ8NKSDW0EahcU=
=P8gN
-----END PGP SIGNATURE-----

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: SUBSTRING performance for large BYTEA
Next
From: "Joshua D. Drake"
Date:
Subject: Re: SUBSTRING performance for large BYTEA