Tom Lane wrote: > Yeah, I think we need to preserve that property. Unexpectedly > executing query (which may have side-effects) is a very dangerous > thing. People are used to the idea that ANALYZE == execute, and > adding random other flags that also cause execution is going to > burn somebody. +1 FWIW, another reason not to use Robert's suggested syntax is that you get "rows=n" entries with or without the actual run. You just don't get the "actual" block to compare to the estimate. So ROWS as an option would be very ambiguous. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
