RES: RES: 8.2.4 selects make applications wait indefinitely
От | Carlos H. Reimer |
---|---|
Тема | RES: RES: 8.2.4 selects make applications wait indefinitely |
Дата | |
Msg-id | PEEPKDFEHHEMKBBFPOOKMEHMFKAA.carlos.reimer@opendb.com.br обсуждение исходный текст |
Ответ на | Re: RES: 8.2.4 selects make applications wait indefinitely ("Scott Marlowe" <scott.marlowe@gmail.com>) |
Ответы |
Re: RES: 8.2.4 selects make applications wait indefinitely
|
Список | pgsql-general |
> On 10/11/07, Carlos H. Reimer <carlos.reimer@opendb.com.br> wrote: > > > "Carlos H. Reimer" <carlos.reimer@opendb.com.br> writes: > > > > SELECT * or naming all the columns locks the client > > > application. Yesterday > > > > I´ve wrongly said that when naming all the columns instead of > > > using the * > > > > the applications did not lock. > > > > > > Hm, are you sure it's not one specific column that's causing the > > > problem? > > Yes, I´ve just doublechecked again. The table has 11 columns, I used 11 > > SELECTs, one for each column, and all run successfully. Started > adding more > > columns, no problem. When the full list of columns was specified in the > > SELECT it locked. > > If you turn on stats_command_string do you see in > > select * from pg_stat_activity; > > for the current_query ??? It´s "<IDLE>" but the "query_start" column is refreshed. Reimer
В списке pgsql-general по дате отправления: