On Sun, Feb 5, 2012 at 12:44 AM, Kevin Grittner <kevin.gritt...@wicourts.gov> wrote: > 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.
OK, so based on that resoundingly unanimous input, I've committed Tomas's last version. I made some alterations to the sgml documentation to avoid mentioning "gettimeofday" specifically, because that might not be the call everywhere (e.g. Windows) and even if it is, it doesn't seem too user-friendly. The code is entirely as he had it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
