Received: from mail.austin.rr.com (sm1.texas.rr.com [24.93.35.54])
	by hub.org (8.9.3/8.9.3) with ESMTP id OAA64786
	for <pgsql-interfaces@postgresql.org>;
	Sun, 5 Mar 2000 14:58:42 -0500 (EST)
	(envelope-from eloehr@austin.rr.com)
Received: from austin.rr.com ([24.93.58.117]) by mail.austin.rr.com with
	Microsoft SMTPSVC(5.5.1877.197.19); Sun, 5 Mar 2000 13:59:27 -0600
Sender: ed
Message-ID: <38C2BD22.45407DFC@austin.rr.com>
Date: Sun, 05 Mar 2000 14:01:38 -0600
From: Ed Loehr <eloehr@austin.rr.com>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "pgsql-interfaces@postgreSQL.org" <pgsql-interfaces@postgresql.org>
Subject: [INTERFACES] RFC: server-side perl for pgsql?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

A recent response in another list got me thinking about how one might
leverage the wealth of functionality available in open source perl
modules.  Specifically, how to do it in the pgsql server rather than
in clients so that clients of all types could take advantage of the
functionality through user-defined db functions.  Personally, I
haven't done anything with user-defined functions beyond fairly
straight-forward PL/pgSQL.  I assume it's possible given it is
possible to call perl functions from C.

Would anyone mind briefly sharing their experience and/or any lessons
learned using server-side perl (or maybe python or tcl) for
user-defined functions in postgresql?  Have these efforts been
successful for you?  What would you do differently if you did it
again?

Regards,
Ed Loehr