Re: explain analyze rows=%.0f - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: explain analyze rows=%.0f
Date
Msg-id ae90d15d-54e5-4caa-ba72-5bbed9b2c908@gmail.com
Whole thread Raw
In response to Re: explain analyze rows=%.0f  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 3/31/25 19:35, Robert Haas wrote:
> But why isn't it just as valuable to have two decimal places for the
> estimate? I theorize that the cases that are really a problem here are
> those where the row count estimate is between 0 and 1 per row, and
> rounding to an integer loses all precision.
Issues I've ever seen were about zero rows number - we lose 
understanding of what the job the executor has done in the node - loops 
= 10000000 doesn't tell us any helpful information in that case.
Maybe in the next version, we replace the two fractional numbers rule 
with two valuable numbers. At least, it removes boring xxx.00 numbers 
from EXPLAIN.

-- 
regards, Andrei Lepikhov



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: add function argument name to substring and substr
Next
From: vignesh C
Date:
Subject: Re: speedup COPY TO for partitioned table.