From: | "Carlos H(dot) Reimer" <carlos(dot)reimer(at)opendb(dot)com(dot)br> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "Pgsql-General(at)Postgresql(dot)Org" <pgsql-general(at)postgresql(dot)org> |
Subject: | RES: RES: 8.2.4 selects make applications wait indefinitely |
Date: | 2007-10-12 02:07:39 |
Message-ID: | PEEPKDFEHHEMKBBFPOOKCEHOFKAA.carlos.reimer@opendb.com.br |
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?
The where clause limits the number of rows returned to 1 only. Only some
primery keys are affected. For example, "Select * from table where pk=1"
works and returns only one line but "select * from table where pk=2" locks
and there is only one line with pk=2 in the table. I believe it is triggered
by something else.
Reimer
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-10-12 02:29:59 | Re: RES: RES: 8.2.4 selects make applications wait indefinitely |
Previous Message | Tom Lane | 2007-10-12 01:58:10 | Re: RES: 8.2.4 selects make applications wait indefinitely |