| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | carlos(dot)reimer(at)opendb(dot)com(dot)br |
| Cc: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Pgsql-General(at)Postgresql(dot)Org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: RES: RES: 8.2.4 selects make applications wait indefinitely |
| Date: | 2007-10-12 02:29:59 |
| Message-ID: | 16377.1192156199@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Carlos H. Reimer" <carlos(dot)reimer(at)opendb(dot)com(dot)br> writes:
>> 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.
Hmm ... are some of the rows particularly wide? It could still be a
data-volume effect ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Wickham | 2007-10-12 03:25:59 | Re: PLPGSQL 'SET SESSION ROLE' problems .. |
| Previous Message | Carlos H. Reimer | 2007-10-12 02:07:39 | RES: RES: 8.2.4 selects make applications wait indefinitely |