Re: Review of: explain / allow collecting row counts without timing info

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Review of: explain / allow collecting row counts without timing info
Дата
Msg-id CA+TgmoZdAG6BJPvQ6bynrnQPOR2gB-X2zZCpNYk-4F7nG+_sog@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Review of: explain / allow collecting row counts without timing info  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Список pgsql-hackers
On Sun, Feb 5, 2012 at 12:44 AM, Kevin Grittner
<Kevin.Grittner@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


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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: patch for parallel pg_dump
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: incorrect handling of the timeout in pg_receivexlog