Re: RES: 8.2.4 selects make applications wait indefinitely
От | Scott Marlowe |
---|---|
Тема | Re: RES: 8.2.4 selects make applications wait indefinitely |
Дата | |
Msg-id | dcc563d10710111806g7ebb10e9r5222f257aa1afe2b@mail.gmail.com обсуждение исходный текст |
Ответ на | RES: RES: 8.2.4 selects make applications wait indefinitely ("Carlos H. Reimer" <carlos.reimer@opendb.com.br>) |
Ответы |
RES: 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 ???
В списке pgsql-general по дате отправления: