"Sabin Coanda" <coanda@xxxxxxxxxx> wrote: > How do you explain the cost is about ten times lower in the 2nd > query than the first ? To elaborate on Pierre's answer: In the first query, you scan the entire table and execute the "f1" function on each row. In the second query you pass the entire table just counting visible tuples and then run the "f1" function once, and use the resulting value to scan an index on which it expects to find one row. It estimates the cost of running the "f1" function 7.7 million times as being roughly ten times the cost of scanning the table. Now, this is all just estimates; if they don't really reflect the relative cost of *running* the two queries, you might want to adjust costs factors -- perhaps the estimated cost of the "f1" function. -Kevin -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
