Re: Why is seq search preferred here by planner? - Mailing list pgsql-sql

From Josh Berkus
Subject Re: Why is seq search preferred here by planner?
Date
Msg-id 200304231000.20578.josh@agliodbs.com
Whole thread Raw
In response to Why is seq search preferred here by planner?  (<mallah@trade-india.com>)
Responses Re: Why is seq search preferred here by planner?  (<mallah@trade-india.com>)
List 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 by date:

Previous
From:
Date:
Subject: Why is seq search preferred here by planner?
Next
From:
Date:
Subject: Re: Why is seq search preferred here by planner?