X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id DBADFD1B8A8 for ; Fri, 5 Sep 2003 02:32:30 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 78330-04 for ; Thu, 4 Sep 2003 23:32:24 -0300 (ADT) Received: from bob.samurai.com (bob.samurai.com [205.207.28.75]) by svr1.postgresql.org (Postfix) with ESMTP id E843FD1B52C for ; Thu, 4 Sep 2003 23:32:19 -0300 (ADT) Received: from 6-allhosts (d226-85-166.home.cgocable.net [24.226.85.166]) by bob.samurai.com (Postfix) with ESMTP id D39771D6B; Thu, 4 Sep 2003 22:32:23 -0400 (EDT) Subject: Re: SELECT's take a long time compared to other DBMS From: Neil Conway To: Relaxin Cc: PostgreSQL Performance In-Reply-To: References: Content-Type: text/plain Message-Id: <1062729142.364.20.camel@tokyo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Thu, 04 Sep 2003 22:32:23 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/86 X-Sequence-Number: 3452 On Thu, 2003-09-04 at 22:13, Relaxin wrote: > Finally, someone who will actually assume/admit that it is returning the > entire result set to the client. > Where as other DBMS manage the records at the server. Is there a reason you can't use cursors (explicitely, or via ODBC if it provides some glue on top of them) to keep the result set on the server? http://candle.pha.pa.us/main/writings/pgsql/sgml/sql-declare.html http://candle.pha.pa.us/main/writings/pgsql/sgml/sql-fetch.html > The next one is the handling of BLOBS. PG handles them like no other system > I have ever come across. Just FYI, you can use both the lo_*() functions, as well as simple bytea/text columns (which can be very large in PostgreSQL). -Neil