On Thu, Mar 6, 2025 at 4:18 PM Alena Rybakina <a.rybak...@postgrespro.ru> wrote: > To be honest, I initially took it as the total number of tuples and > couldn't figure out for myself how to interpret the result - 0 tuples or > 1 tuple in the end. Maybe it wasn't quite correct to perceive it that > way, but Matthias's explanation helped me figure out the reason why such > a strange result was obtained, although it's not usual to see it.
Yeah, I thought the same back when I first started using PostgreSQL and had to learn that it wasn't the case. I still think that's what we *should* be displaying -- I think dividing by nloops obscures the data users actually want. But it would admittedly be a pretty big compatibility break at this point, and at least if we display a couple of decimal places it's more possible to approximate the undivided value. -- Robert Haas EDB: http://www.enterprisedb.com
