Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] Use Declare/Fetch option

From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: pgsql-interfaces <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: Re: [INTERFACES] Use Declare/Fetch option
Date: 1999-01-27 15:59:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces

Hiroshi Inoue wrote:

> Hello all,
> I have a question about psqlodbc driver.
> Now the default setting for "Use Declare/Fetch" is false.
> In MVCC thanks to Vadim,readers block no writers.
> So we can change the [Use Declare/Fetch] option to true ?
> And if so,it's effective ?

All you say is correct.   It probably could go back to true.  But I
think some people would probably prefer it stay false, because there is
more odbc functionality provided with this setting.  For example, when
the option is false, the entire SQLExtendedFetch functionality is
supported (prev,first,last,next,absolute,relative,bookmark).  When the
Declare/Fetch option is true, only fetch "next" is supported.  There are
more things like this.

If you have extremely large result sets, then setting the option to true
would prevent the driver from sucking down all your memory.   And when
the MVCC is available, the problem of locking rows won't be a problem
anymore.  For small to medium result sets, setting the option to false
will probably result in faster performance.

A future enhancement I have in mind for the driver is using both memory
and files for caching large result sets and/or using a combination of
both kinds of tuple access.


> Thanks.
> Hiroshi Inoue
> Inoue(at)tpf(dot)co(dot)jp

In response to

pgsql-interfaces by date

Next:From: Paulo Ricardo SikorskiDate: 1999-01-28 12:00:37
Subject: pgaccess troubles with crypt
Previous:From: Ralf BergerDate: 1999-01-27 15:32:26
Subject: Re: [INTERFACES] Question about libpq++

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group