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

From Andrei Lepikhov
Subject Re: explain analyze rows=%.0f
Date
Msg-id c9f91659-f17d-41f4-ad16-2801cf61b608@gmail.com
Whole thread Raw
In response to Re: explain analyze rows=%.0f  (Ilia Evdokimov <ilya.evdokimov@tantorlabs.com>)
List pgsql-hackers
On 19/2/2025 15:01, Ilia Evdokimov wrote:
> If we want to convey this information more clearly, we should consider a 
> more explicit approach. For example, instead of using a fractional 
> value, we could display the minimum and maximum row counts observed 
> during execution (e.g.,rows=10..20, formatting details could be 
> discussed). However, in my opinion, this discussion is beyond the scope 
> of this thread.
I think this approach is redundant. Usually, a problem is an unknown 
number of tuples because, having millions of loops, we produce a small 
number of tuples, but each tuple costs a lot because of a subplan or 
something like that. By printing fractional digits (of course, we need 
to view significant ones, but we already agreed on a couple of digits 
for now), we may resolve this corner-case problem fully - at least all 
examples in my experience would be resolved, and I have even maintained 
a patch for years to manage this.
Moreover, it is too simple to implement. I just can't imagine why not to 
do it right now.

-- 
regards, Andrei Lepikhov



pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: new commitfest transition guidance
Next
From: Andres Freund
Date:
Subject: Re: BackgroundPsql swallowing errors on windows