Re: Postgresql goes into recovery mode ....

Поиск
Список
Период
Сортировка
Искать
От
Rajesh Kumar Mallah
Тема
Re: Postgresql goes into recovery mode ....
Дата
Msg-id
3CB52E8B.A7103324@trade-india.com
Список
Дерево обсуждения
Re: Postgresql goes into recovery mode .... Rajesh Kumar Mallah <mallah@trade-india.com>
Re: Postgresql goes into recovery mode .... Jeff Eckermann <jeff_eckermann@yahoo.com>
   
jeff  i feel  the  second subselect is  required  becoz *without* the where clause the
query:

UPDATE  email_bank set userid=(select userid  from t_a where
email_id=email_bank.email_id)

would have updated *all* records in email_bank  (1 million) where as
i want to update only 35 K in those which are in t_a  so "exists" is reqd.

i also feel UPDATE .. FROM  is better Sql for this purpose which
can be written as:

update  email_bank set userid=t_a.userid from t_a
where t_a.email_id = email_bank.email_id ;
 

the above also puts  my SQL in  abnormnal state.

Yes Jean  UPDATE .. FROM works in 7.1.3.

acutally  what i want to know  is even if my SQL were wrong
what is the way out  from  the recovery mode? and less importantly
is my SQL really wrong?

regds
mallah.
 
 
 

Jean-Luc Lachance wrote:

If I reacall, it (UPDATE ... FROM) does not work with 7.1.
I think it was added only in 7.2.

 way is the only way with 7.1.

Bottom line Rajesh: you should upgrade to 7.2.1

JLL

Jeff Eckermann wrote:
>
> I think the second subselect (in the EXISTS clause) is
> not necessary, as it will always return true if the
> where clause in the first subselect (in the SET
> clause) is satisfied.
>
> Another way to write it (untested):
> update email_bank set userid = t_a.userid
> where email_id = t_a.email_id;
>
> --- Rajesh Kumar Mallah <mallah@trade-india.com>


 
(consult mailing list )
В списке pgsql-sql по дате отправления
От: jeff fitzmyers
Дата:
От: Rajesh Kumar Mallah
Дата:
FAQ