From: Sbragion Denis <infotecn@tin.it>
To: Greg Youngblood <YoungblG@houstoncellular.com>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Problems with queries on small/medium sized tables
Date: Wed, 16 Sep 1998 09:03:49 +0200
Message-ID: <3.0.6.32.19980916090349.00807d10@MBox.InfoTecna.com> (raw)
In-Reply-To: <2B9713A99045D211BB4E0008C75668690B0FFE@SCORPEXC1.houstonce ll.com>
Hello,
At 13.00 15/09/98 -0500, you wrote:
>I am having a problem with queries.
>
...
>The following query is used:
> SELECT usage.*
> FROM usage
> WHERE
> (((usage.yyyymmdd) Between 19980701 And 19980731)
> AND ((usage.link)='swbt08')) OR (((usage.link)='swbtja'))
> ORDER BY
> usage.yyyymmdd, usage.hhmm, usage.stp, usage.link;
>
>When run from psql the answer is returned fairly quickly. When run from
>Access via ODBC, the system memory starts increasing until it gets to 60/70%
>on the single postgres process, and CPU is usually below 10% (normal queries
>shoot CPU up to 50 to 99 % and memory stays around 3 to 8 percent). Then the
>ODBC call fails and Access doesn't get any information.
the jet database engine often parses and rewrites queries to get simpler
ones. Sometimes these simpler queries contain many "OR" in the where clause
and the backend optimizer crashes on them. Use the trace feature of the
ODBC to see exactly which kind of queries are sent to the backend. To solve
it you have to use passthrough queries, but I have no idea how this can be
done in Access.
Hope it helps.
Bye!
Dr. Sbragion Denis
InfoTecna
Tel, Fax: +39 39 2324054
URL: http://space.tin.it/internet/dsbragio
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 using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: infotecn@tin.it, YoungblG@houstoncellular.com
Subject: Re: [INTERFACES] Problems with queries on small/medium sized tables
In-Reply-To: <3.0.6.32.19980916090349.00807d10@MBox.InfoTecna.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