| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | carlos(dot)reimer(at)opendb(dot)com(dot)br, "Pgsql-General(at)Postgresql(dot)Org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: RES: 8.2.4 selects make applications wait indefinitely |
| Date: | 2007-10-12 01:58:10 |
| Message-ID: | 15958.1192154290@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> writes:
> On 10/11/07, Carlos H. Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br> wrote:
>> It=B4s "<IDLE>" but the "query_start" column is refreshed.
> Then the query runs and finishes and the problem is something to do
> with the delivery of the data. Not sure after that...
That seems to eliminate the possibility that the problem is on the
server side. I'd suggest trying to get a stack trace from the client
to figure out what it's doing.
BTW, have you looked into the theory that it's triggered by total
data volume rather than number of columns? That is, try selecting
all the columns but use LIMIT to reduce the number of rows fetched?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Carlos H. Reimer | 2007-10-12 02:07:39 | RES: RES: 8.2.4 selects make applications wait indefinitely |
| Previous Message | Scott Marlowe | 2007-10-12 01:32:33 | Re: RES: 8.2.4 selects make applications wait indefinitely |