From: | "Carlos H(dot) Reimer" <carlos(dot)reimer(at)opendb(dot)com(dot)br> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Pgsql-General(at)Postgresql(dot)Org" <pgsql-general(at)postgresql(dot)org> |
Subject: | RES: RES: 8.2.4 selects make applications wait indefinitely |
Date: | 2007-10-12 01:18:00 |
Message-ID: | PEEPKDFEHHEMKBBFPOOKMEHMFKAA.carlos.reimer@opendb.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 10/11/07, Carlos H. Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br> wrote:
> > > "Carlos H. Reimer" <carlos(dot)reimer(at)opendb(dot)com(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-10-12 01:32:33 | Re: RES: 8.2.4 selects make applications wait indefinitely |
Previous Message | Scott Marlowe | 2007-10-12 01:06:15 | Re: RES: 8.2.4 selects make applications wait indefinitely |