On 10/11/07, Carlos H. Reimer <carlos.reimer@opendb.com.br> wrote:
> > 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.
Then the query runs and finishes and the problem is something to do
with the delivery of the data. Not sure after that...