Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tiHeu-00DvtS-5U for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Feb 2025 18:40:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tiHes-00CJbK-1Q for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Feb 2025 18:40:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tiHer-00CJbB-Nv for pgsql-hackers@lists.postgresql.org; Wed, 12 Feb 2025 18:40:26 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tiHeq-000U59-13 for pgsql-hackers@lists.postgresql.org; Wed, 12 Feb 2025 18:40:26 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 51CIeFFp3365161; Wed, 12 Feb 2025 13:40:15 -0500 From: Tom Lane To: Robert Haas cc: Ilia Evdokimov , Andrei Lepikhov , Matheus Alcantara , Guillaume Lelarge , Daniel Gustafsson , Ibrar Ahmed , "Gregory Stark (as CFM)" , Amit Kapila , Justin Pryzby , Peter Geoghegan , vignesh C , "David G. Johnston" , pgsql-hackers@lists.postgresql.org Subject: Re: explain analyze rows=%.0f In-reply-to: References: <55695d15-c738-4401-8883-58bc855c9b03@tantorlabs.com> <58bb3a5b-c92a-408c-b02a-f47aedc1c0e2@tantorlabs.com> <70bc1af0-6910-4f71-84ba-fa02095fe9ba@tantorlabs.com> <3212947.1739306803@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Wed, 12 Feb 2025 13:19:11 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3365159.1739385615.1@sss.pgh.pa.us> Date: Wed, 12 Feb 2025 13:40:15 -0500 Message-ID: <3365160.1739385615@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > I agree that showing 2 digits after the decimal point in all cases is > not ideal, but I suggest that we take a practical approach. Figuring > out dynamically what number of decimal digits to display in each case > sounds complicated and we may spend a bunch of time arguing about the > details of that and get nothing committed. If we just show 2 digits > after the decimal point, it will not be perfect, but it will be 10^2 > times better than what we have now. I was idly speculating yesterday about letting the Ryu code print the division result, so that we get a variable number of digits. Realistically, that'd probably result in many cases in more digits than anybody wants, so it's not a serious proposal. I'm cool with the fixed-two-digits approach to start with. regards, tom lane