Re: explain analyze rows=%.0f
От | Ilia Evdokimov |
---|---|
Тема | Re: explain analyze rows=%.0f |
Дата | |
Msg-id | 40663fc5-edac-4b45-a2aa-a76976700ed9@tantorlabs.com обсуждение исходный текст |
Ответ на | Re: explain analyze rows=%.0f (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: explain analyze rows=%.0f
|
Список | pgsql-hackers |
On 24.02.2025 19:20, Robert Haas wrote: > On Fri, Feb 21, 2025 at 10:00 PM Robert Haas <robertmhaas@gmail.com> wrote: >> I guess we could do that, but how about just always displaying two >> decimal places? I feel like you're really worried that people will be >> confused if the row count is not an integer, but I'm not sure anyone >> else has echoed that concern, and I am doubtful that it's really a >> problem. Either people don't understand that the row count is divided >> through by nloops, in which case the decimal places might actually >> give them a clue that they've misunderstood, or they do understand >> that, in which case the decimal places are not confusing. I feel like >> we've gone to a lot of trouble to come up with complex solutions -- >> what was actually committed was one of the simpler things proposed -- >> but I am still not convinced that the simplest solution isn't for the >> best. > So here's a patch for that. Thoughts? > If no one is concerned about rows being a non-integer, then I support this, as it's quite strange for the average rows to be an integer only for me. If we go with this approach, we should also update all examples in the documentation accordingly. I attached patch with changes in documentation. -- Best regards, Ilia Evdokimov, Tantor Labs LLC.
Вложения
В списке pgsql-hackers по дате отправления: