pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Relaxin <noname@spam.com>
To: pgsql-performance@postgresql.org
Subject: Re: SELECT's take a long time compared to other DBMS
Date: Thu, 4 Sep 2003 21:59:01 -0700
Message-ID: <bj9565$2n3l$1@news.hub.org> (raw)
References: <bj611t$1o2g$1@news.hub.org>
	<bj7tlm$ngt$1@news.hub.org>
	<bj8h0o$dq4$1@news.hub.org>
	<m3fzjc58ll.fsf@chvatal.cbbrowne.com>
	<bj8rfn$1hep$1@news.hub.org>
	<1062729142.364.20.camel@tokyo>

> 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





view thread (34+ messages)  latest in thread

Message-ID: <bj9565$2n3l$1@news.hub.org>
Permalink:  ../bj9565$2n3l$1@news.hub.org/
Also on:    postgresql.org/message-id/bj9565$2n3l$1@news.hub.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: noname@spam.com
  Subject: Re: SELECT's take a long time compared to other DBMS
  In-Reply-To: <bj9565$2n3l$1@news.hub.org>
  References: <bj611t$1o2g$1@news.hub.org> <bj7tlm$ngt$1@news.hub.org> <bj8h0o$dq4$1@news.hub.org> <m3fzjc58ll.fsf@chvatal.cbbrowne.com> <bj8rfn$1hep$1@news.hub.org> <1062729142.364.20.camel@tokyo> <bj9565$2n3l$1@news.hub.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox