On 10/11/07, Carlos H. Reimer <carlos.reimer@xxxxxxxxxxxxx> wrote:
> > "Carlos H. Reimer" <carlos.reimer@xxxxxxxxxxxxx> 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 ???
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
