Re: Access 2003 reports queries taking very long

On Sat, Feb 15, 2014 at 5:43 AM, Luca Ferrari <fluca1978(at)infinito(dot)it> wrote:

> On Wed, Feb 12, 2014 at 3:53 PM, Andrew Puschak <apuschak(at)gmail(dot)com>
> wrote:
> > 2014-02-12 09:14:00 EST [18238]: [16-1] user=ourcompany,db=ourcompany
> LOG: duration: 6231.878 ms statement: SELECT "savedt" ,"clid_name" ,"hrs"
> ,"purpose" ,"howlong" FROM "public"."ourtable"
>
> > 2014-02-12 09:14:22 EST [18238]: [17-1] user=ourcompany,db=ourcompany
> LOG: duration: 18596.817 ms statement: SELECT "savedt" ,"jobid" ,"emid"
> ,"clid_name" ,"hrs" ,"jname" ,"lname" ,"purpose" ,"howlong" ,"clid"
> ,"w_min" ,"m1" FROM "public"."ourtable"
>
>
> The only difference I see is in the number of columns, but it is quite
> strange that having the two queries ran at such a small time the data
> is not cached. Is there anything that happened on the cluster (even
> outside outable) in the meantime?
>
>
> Luca
>

Hi Luca,

Thank you for your reply. I'm not sure what you mean by anything else
happening? We have a lot of queries throughout the day, however there's
nothing abnormal when these long queries occur in the postgres log. The
postgres log is logging every query for pgBadger so it should show if
there's something else going on at that time I think. The only difference
seems to be that they come from Access through the ODBC connector. We are
only using one database in the cluster and everything is relatively simple,
although high volume.

Andrew