I fooled myself for a while by accidently turning tracing on in the
ODBC driver manager (under the tracing tab). This slowed everything down
while I was trying to work out why my new shiney view was so sloooowwwwwww
:). Also check the commlog driver option is unchecked.
If you find a query doing the same find but in a where condition (eg
SELECT * FROM tbl WHERE col=1234) then it might be the additional reading
its doing to set up all the other data seen on the grid. Try starting the
postmaster with -d2 to see if that gives usefull info on the queries being
executed.
- Stuart
> -----Original Message-----
> From: Alejandro Alfonso Fernandez [SMTP:kawa@enete.gui.uva.es]
> Sent: Wednesday, October 10, 2001 11:00 AM
> To: pgsql-odbc@postgresql.org
> Subject: PgSQL vs Ms.Access slow in search
>
>
> Hello everybody!
>
> First of all, sorry for my poor english. And now, the problem
> that don't leave me sleep :). I'm using PgSQL as the data source of some
> forms in MsAccess, with the current version of the ODBC driver. It
> exports/imports tables right and fast. But... when I have the tables
> "linked" (it's correct this word???), and i try to do a search (Edit->Find
> or Ctrl-B) in any column of any table with more of 1.000 tuples:
> first: the access seems to be dead thinking too much :)
> second: the postmaster takes 99% of CPU
> Why????? In numerics primary keys, the both works better, but most of
> time, they dead.
>
> I've startde postmaster from a shell, and I get:
> 2001-10-09 20:39:50 [6573] DEBUG: StartTransactionCommand
> 2001-10-09 20:39:51 [6573] DEBUG: CommitTransactionCommand
> 2001-10-09 20:39:51 [6573] DEBUG: StartTransactionCommand
> 2001-10-09 20:39:51 [6573] DEBUG: CommitTransactionCommand
> 2001-10-09 20:39:51 [6573] DEBUG: StartTransactionCommand
> 2001-10-09 20:39:51 [6573] DEBUG: CommitTransactionCommand
> 2001-10-09 20:39:51 [6573] DEBUG: StartTransactionCommand
> 2001-10-09 20:39:51 [6573] DEBUG: CommitTransactionCommand
> 2001-10-09 20:39:51 [6573] DEBUG: StartTransactionCommand
> 2001-10-09 20:39:52 [6573] DEBUG: CommitTransactionCommand
> (only 4 querys from each second?????)
>
> I've tried to fin a solution by my self, but I couldn't :(. With MySQL ->
> MyODBC -> Access the problem It's the same.
>
> Thanks in advance from Spain...
>
> _____ - - - - - - - - - Alejandro Alfonso Fernández - - - - - - - -
> -
> /\___/\ Grupo Universitario de Informática - Diplomatura en
> Estadística
> /__\ _\/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> -
> /_/\_\ - "Lo mejor de tu ordenador está entre tu silla y tu teclado"
> -
> /_/ /\_\ Atari Php Asp Wap Sql Dhtml Swf JavaScript Java Xml C Awk
> Sed
> \_\/ \_\ - Email: kawa@gui.uva.es - Web: http://www.gui.uva.es/~kawa/
> -
> L.Carrol: Hace falta que corras todo lo que puedas para seguir en el
> mismo
> sitio. Si quieres ir a alguna parte, tendras que correr el doble de
> rapido!
> *gpg*public*key->http://www.gui.uva.es/%7ekawa/alexokawa.gpg<-gpg*public*k
> ey
>
