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 06E833A57DF for ; Tue, 11 Jan 2005 00:04:46 +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 62450-03 for ; Tue, 11 Jan 2005 00:04:40 +0000 (GMT) Received: from net2.micro-automation.com (net2.micro-automation.com [64.7.141.29]) by svr1.postgresql.org (Postfix) with SMTP id 301863A57D0 for ; Tue, 11 Jan 2005 00:04:42 +0000 (GMT) Received: (qmail 26426 invoked from network); 11 Jan 2005 00:04:11 -0000 Received: from dcdsl.ebox.com (HELO ?192.168.1.36?) (davec@64.7.143.116) by net2.micro-automation.com with SMTP; 11 Jan 2005 00:04:11 -0000 Message-ID: <41E31815.4030908@fastcrypt.com> Date: Mon, 10 Jan 2005 19:04:37 -0500 From: Dave Cramer Reply-To: pg@fastcrypt.com Organization: Postgres International User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gary Doades 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> In-Reply-To: <41E2F9ED.1070206@gpdnet.co.uk> 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.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/117 X-Sequence-Number: 9807 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. Dave Gary Doades wrote: > Dave Cramer wrote: > >> I'm curious, why do you think that's serious ? What do you really >> expect to do in the stored procedure ? Anything of consequence will >> seriously degrade performance if you select it in say a million rows. >> > > I'm not sure what you mean by "select it in a million rows". I would > expect to write a procedure within the database engine to select a > million rows, process them and return the result to the client. Very > efficient. > > Cheers, > Gary. > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > > -- Dave Cramer http://www.postgresintl.com 519 939 0336 ICQ#14675561