pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Albert Cervera Areny <albertca@jazzfree.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-odbc@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Bad performance using ODBC
Date: Thu, 17 Jul 2003 18:14:16 +0200
Message-ID: <200307171814.35145.albertca@jazzfree.com> (raw)
In-Reply-To: <18118.1058366296@sss.pgh.pa.us>
References: <200307161615.13989.albertca@jazzfree.com>
	<18118.1058366296@sss.pgh.pa.us>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A Dimecres 16 Juliol 2003 16:38, Tom Lane va escriure:
> Albert Cervera Areny <albertca@jazzfree.com> writes:
> >   I have a performance problem using postgresql when the connection is
> > made via ODBC with a windows machine using the latests ODBC drivers
> > (Windows) and PostgreSQL 7.3.3 (Linux).
>
> Do you have logging turned on in the ODBC driver?  I recall hearing that
> that adds a heck of a lot of overhead...

After trying too many things I've finally been able to make it run in just 1 
or 2 seconds. I simply had to change the recordset type and set it to 
dbOpenSnapshot (This one doesn't show changes made to the database once it's 
been open) instead of the default dbDynaset (much more powerful but 
unnecessary in this application).

Take note that though it might seem obvious the performance loss against 
Access isn't that much and thus VB users aren't probably used to change the 
recordset type. I think It would be nice a note with this performance 
benchmarks (2 seconds against 15) in the Mini-Howto on Accessing PostgreSQL 
from Visual Basic. I'll contact Dave Page directly in case he finds it 
interesting.

I haven't seen any speed improvements desabling logging but thanks for your 
suggestion anyway!

>
> 			regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/FstfTK7ZP4pDOHcRArepAJ9rIhOKtztuPORbGkrVTOfC4UmUOQCeJ00u
UxJegkvrs4TL3QVXNun3iFs=
=itG7
-----END PGP SIGNATURE-----



view thread (3+ messages)

Message-ID: <200307171814.35145.albertca@jazzfree.com>
Permalink:  ../200307171814.35145.albertca@jazzfree.com/
Also on:    postgresql.org/message-id/200307171814.35145.albertca@jazzfree.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: albertca@jazzfree.com, tgl@sss.pgh.pa.us, pgsql-odbc@postgresql.org
  Subject: Re: [PERFORM] Bad performance using ODBC
  In-Reply-To: <200307171814.35145.albertca@jazzfree.com>
  References: <200307161615.13989.albertca@jazzfree.com> <18118.1058366296@sss.pgh.pa.us> <200307171814.35145.albertca@jazzfree.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