X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8B8883A55CB for ; Tue, 11 Jan 2005 07:39:14 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 30815-02 for ; Tue, 11 Jan 2005 07:39:11 +0000 (GMT) Received: from server.gpdnet.co.uk (gpdnet.plus.com [212.56.100.243]) by svr1.postgresql.org (Postfix) with ESMTP id 940593A55BA for ; Tue, 11 Jan 2005 07:39:09 +0000 (GMT) Received: from [192.168.1.2] (unknown [192.168.1.2]) by server.gpdnet.co.uk (Postfix) with ESMTP id C1E913AAD6E for ; Tue, 11 Jan 2005 07:42:38 +0000 (GMT) Message-ID: <41E38231.5090301@gpdnet.co.uk> Date: Tue, 11 Jan 2005 07:37:21 +0000 From: Gary Doades User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: pgsql-performance@postgresql.org Subject: Re: PostgreSQL vs. Oracle vs. Microsoft References: <41E22F04.103@gpdnet.co.uk> <33c6269f05011008074b33b812@mail.gmail.com> <20050110173307.GA18357@zong.spline.inf.fu-berlin.de> <20050110114200.76e9a51d.frank@wiles.org> <33c6269f050110094646897c3e@mail.gmail.com> <41E2E19D.1000903@gpdnet.co.uk> <41E2F43C.5020702@fastcrypt.com> <41E2F9ED.1070206@gpdnet.co.uk> <41E31815.4030908@fastcrypt.com> In-Reply-To: <41E31815.4030908@fastcrypt.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/126 X-Sequence-Number: 9816 Dave Cramer wrote: > Ok, so one use case is to select a large number of rows and do some > non-trivial operation on them. > I can see where getting the rows inside the server process ( ie some > procedural language ) thereby reducing the round trip overhead would be > beneficial. However how do you deal with the lack of control ? For > instance what happens if you run out of memory while doing this ? I'm > not sure about other DB'S but if you crash the procedural language > inside postgres you will bring the server down. > > It would seem to me that any non-trivial operation would be better > handled outside the server process, even if it costs you the round trip. Since a .NET language is operating effectively inside a VM it is pretty much impossible to bring down the server that way. Only a bug in the .NET runtime itself will do that. The C# try/catch/finally with .NET global execption last chance handlers will ensure the server and your code is well protected. Cheers, Gary.