Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1LL6fx29176 for ; Wed, 21 Feb 2001 16:06:41 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f1LL4f912095; Wed, 21 Feb 2001 16:04:42 -0500 (EST) To: Jie Liang cc: Jeff MacDonald , Alex Pilosov , pgsql-sql@postgresql.org Subject: Re: pl/Perl In-reply-to: References: Comments: In-reply-to Jie Liang message dated "Wed, 21 Feb 2001 12:38:02 -0800" Date: Wed, 21 Feb 2001 16:04:41 -0500 Message-ID: <12092.982789481@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/329 X-Sequence-Number: 1525 Jie Liang writes: > My choice: > if involving a lot of regular expressions, pl/Perl is better; > if involving a lot of SQLs or other functions(or store procedures), > then pl/pgsql is better. Also consider pltcl, which has pretty nearly perl-equivalent regexp support, and can do queries too. Besides which it's easier to build/ install than plperl. It's a shame that plperl doesn't yet have support for making queries. It hasn't really progressed much past the proof-of-concept stage IMHO, but no one is working on it :-( regards, tom lane