| From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
|---|---|
| To: | Andrew Puschak <apuschak(at)gmail(dot)com> |
| Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Access 2003 reports queries taking very long |
| Date: | 2014-02-15 10:43:31 |
| Message-ID: | CAKoxK+6tBJbX61Zd9dL-FNrPHHFsZ=wWh0dbZVN-CPPfxX4CDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | avpro avpro | 2014-02-15 11:18:12 | |
| Previous Message | Andrew Puschak | 2014-02-12 14:53:28 | Access 2003 reports queries taking very long |