From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | carlos(dot)reimer(at)opendb(dot)com(dot)br |
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: | Re: RES: 8.2.4 selects make applications wait indefinitely |
Date: | 2007-10-12 01:06:15 |
Message-ID: | dcc563d10710111806g7ebb10e9r5222f257aa1afe2b@mail.gmail.com |
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 ???
From | Date | Subject | |
---|---|---|---|
Next Message | Carlos H. Reimer | 2007-10-12 01:18:00 | RES: RES: 8.2.4 selects make applications wait indefinitely |
Previous Message | Carlos H. Reimer | 2007-10-11 22:29:33 | RES: RES: 8.2.4 selects make applications wait indefinitely |