Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id B966E633066 for ; Thu, 19 Feb 2009 08:40:00 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 51433-06 for ; Thu, 19 Feb 2009 08:39:55 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from emerald.lightlink.com (emerald.lightlink.com [64.57.176.19]) by mail.postgresql.org (Postfix) with ESMTP id 6B694632629 for ; Thu, 19 Feb 2009 08:39:52 -0400 (AST) Received: from [172.16.10.72] (cpe-24-58-18-216.twcny.res.rr.com [24.58.18.216]) by emerald.lightlink.com (8.9.3p2/8.8.8) with ESMTP id HAA32183; Thu, 19 Feb 2009 07:39:47 -0500 Message-ID: <499D530C.101@lightlink.com> Date: Thu, 19 Feb 2009 07:39:40 -0500 From: Bob McConnell User-Agent: Thunderbird 2.0.0.17 (X11/20080914) MIME-Version: 1.0 To: =?UTF-8?B?IlJvZHJpZ28gRS4gRGUgTGXDs24gUGxpY2V0Ig==?= CC: pgsql-php@postgresql.org Subject: Re: pl/php for windows References: <873a98c60902180641u2320846bq4261bde13d59dd7a@mail.gmail.com> <499CAA23.3050504@lightlink.com> <1235005446.22166.31.camel@happy.mcmillan.net.nz> <499CCC25.80200@lightlink.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200902/14 X-Sequence-Number: 3990 Rodrigo E. De León Plicet wrote: > On Wed, Feb 18, 2009 at 10:04 PM, Bob McConnell wrote: >> (...) we have a company policy forbidding stored procedures (...) > > Why would that be? > > Just curious... > There are a couple of reasons. First, even when written in SQL, stored procedures are not all that portable. In addition to Postgres, our systems use Oracle, Sybase ASA and Microsoft SQL Server. That's what happens when you buy and absorb other companies. Fortunately, the primary application I work with only supports Postgres. It is happily processing tens of thousands of transactions each day. Second, some of those servers are very slow when running stored procedures and we don't have time to spend optimizing procedures for each server. It's even more difficult for the Oracle servers which we don't manage. We will only support that option when the client already has a site license and full time DBA. Now, there are a few instances where a case has been made and accepted to use some specific stored procedures. But that choice is always made on a case by case basis, with significant evaluation backing up the decision. More requests have been turned down than accepted. Bob McConnell N2SPP