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 613CAD1B89E for ; Fri, 5 Sep 2003 05:25:14 +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 91102-08 for ; Fri, 5 Sep 2003 02:25:04 -0300 (ADT) Received: from news.hub.org (unknown [64.117.224.194]) by svr1.postgresql.org (Postfix) with ESMTP id B8856D1B897 for ; Fri, 5 Sep 2003 02:25:03 -0300 (ADT) Received: from news.hub.org (host-64-117-224-194.altec1.com [64.117.224.194] (may be forged)) by news.hub.org (8.12.9/8.12.9) with ESMTP id h855P3Df094663 for ; Fri, 5 Sep 2003 05:25:03 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id h854wkkD089211 for pgsql-performance@postgresql.org; Fri, 5 Sep 2003 04:58:46 GMT From: "Relaxin" X-Newsgroups: comp.databases.postgresql.performance Subject: Re: SELECT's take a long time compared to other DBMS Date: Thu, 4 Sep 2003 21:59:01 -0700 Organization: Hub.Org Networking Services Lines: 38 Message-ID: References: <1062729142.364.20.camel@tokyo> X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/88 X-Sequence-Number: 3454 > 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 I can only use generally accepted forms of connectivity (ie. ODBC, ADO or OLEDB). This is what many of the people on the Windows side are going to need, because most of us are going to be converting from an existing already established system, such as Oracle, SQL Server or DB2, all of which have 1 or more of the 3 mentioned above. > > 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 I know PG has a ODBC driver (that's all I've been using), but it or PG just doesn't handle BLOBS the way people on the Windows side (don't know about Unix) are use too. There is this conversion to octet that must be performed on the data , I don't understand why, but I guess there was a reason for it long ago, but it seems that it can now be modified to just accept ANY byte you give it and then store it without any manipulation of the data. This will make Postgresql much more portable for the Windows developers...no need for any special handling for a data type that all large RDBMS support. Thanks