Re: Why is seq search preferred here by planner?

Поиск
Список
Период
Сортировка
От Josh Berkus
Тема Re: Why is seq search preferred here by planner?
Дата
Msg-id 200304231000.20578.josh@agliodbs.com
обсуждение исходный текст
Ответ на Why is seq search preferred here by planner?  (<mallah@trade-india.com>)
Ответы Re: Why is seq search preferred here by planner?  (<mallah@trade-india.com>)
Список pgsql-sql
Mallah,

> UPDATE email_bank set country=personal_account_details.country where userid
> > 0 and userid=personal_account_details.userid  ;

While Postgres is letting you "fudge", you are missing part of that SQL
statement.  It should be:
UPDATE email_bank set country=personal_account_details.countryFROM personal_account_detailswhere userid > 0 and
userid=personal_account_details.userid ; 

> tradein_clients=# begin work;explain analyze UPDATE email_bank set
> country=personal_account_details.country where userid > 0 and
> userid=personal_account_details.userid  ;BEGIN
> Time: 669.57 ms

Hmmm ... 669 ms seems pretty speedy for updating 150,000 rows.   What's the
problem?

--
Josh Berkus
Aglio Database Solutions
San Francisco



В списке pgsql-sql по дате отправления:

Предыдущее
От:
Дата:
Сообщение: Why is seq search preferred here by planner?
Следующее
От:
Дата:
Сообщение: Re: Why is seq search preferred here by planner?