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

Re: bad performance for Access, ODBC and Postgres

From: Jean-Max Reymond <jmreymond(at)gmail(dot)com>
To: Eric HAGENBACH <eric(dot)hagenbach(at)vif(dot)tm(dot)fr>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: bad performance for Access, ODBC and Postgres
Date: 2004-07-29 13:18:52
Message-ID: 4b09a0c0407290618a54b072@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-odbc
On Thu, 29 Jul 2004 14:57:25 +0200, Eric HAGENBACH
<eric(dot)hagenbach(at)vif(dot)tm(dot)fr> wrote:
> Jean-Max Reymond a écrit :
> 
> >Hi,
> >I have very poor access whith a front end Access 2003, ODBC and Postgres 7.4.3.
> >Much time to find a record in a table ff 13000 records with indexs.
> >Sniffing the network, I can see a lot of traffic and the CPU of
> >postmaster is about 30% (P4, 2.8 GHz). It seems that all the data's
> >are backed on the client side and then, analyzed.
> >Does it exist an option to improve the performances ?
> >thanks,
> >
> >
> >
> Maybe you can use the EXPLAIN command to see what query plan the system
> creates for your query (you can see the where condition,  which index is
> used, ...)
> 
> Eric.
> 

EXPLAIN is for identified requests and I don't know which request Access sends.
It seems that Access open a cursor on the database and reads each
record one by one and tries to match with the condition. This is the
only way  I can explain such behaviour and it is of course very silly.

-- 
Jean-Max Reymond
CKR Solutions
http://www.ckr-solutions.com

In response to

pgsql-odbc by date

Next:From: Philippe LangDate: 2004-07-29 13:23:57
Subject: Re: bad performance for Access, ODBC and Postgres
Previous:From: Eric HAGENBACHDate: 2004-07-29 12:57:25
Subject: Re: bad performance for Access, ODBC and Postgres

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