pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Robert John Shepherd <robert@reviewer.co.uk>
To: pgsql-performance@postgresql.org
Subject: Re: Best ODBC cursor and lock types for fastest reading?
Date: Tue, 29 Apr 2003 08:38:50 -0700
Message-ID: <200304290838.50503.josh@agliodbs.com> (raw)
In-Reply-To: <001701c30e56$b0964400$f3b0313e@LAIKA>
References: <001701c30e56$b0964400$f3b0313e@LAIKA>

Robert,

> The following options are defined in ADO with which I can create a
> recordset with:
<snip>
> Do any of these offer a performance gain over others? I used to use
> adLockReadOnly with MS-SQL which really sped things up but this doesn't
> seem to work at all under Postgresql and I've been using
> adLockOptimistic instead.

All of the types you list were designed around the MS SQL/MSDE server 
architecture, and many do not apply to PostgreSQL (for example, Postgres does 
not use read locks and does not support client-side keyset cursors as far as 
I know).   I wouldn't be surprised to find out that the pgODBC driver is 
ignoring most of these options as irrelevant -- you should contact the pgODBC 
project to find out.

Certainly I wouldn't expect any setting other than adLockPessimistic to have 
an effect on the speed at which you get rows from the server (Pessimistic 
would presumably declare "SELECT FOR UPDATE", which would be slower).   
However, one or more types might be faster on the client side than the 
others; I recommmend that you set up a test case and experiment.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco




view thread (3+ messages)  latest in thread

Message-ID: <200304290838.50503.josh@agliodbs.com>
Permalink:  ../200304290838.50503.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200304290838.50503.josh@agliodbs.com

 · 

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: josh@agliodbs.com, robert@reviewer.co.uk
  Subject: Re: Best ODBC cursor and lock types for fastest reading?
  In-Reply-To: <200304290838.50503.josh@agliodbs.com>
  References: <001701c30e56$b0964400$f3b0313e@LAIKA> <200304290838.50503.josh@agliodbs.com>

* 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