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

From Gregory Stark (as CFM)
Subject Re: explain analyze rows=%.0f
Date
Msg-id CAM-w4HNLRO8QJvF3x13wjjdkJHobORxaKrcuyF1cKaTiXuvDbA@mail.gmail.com
Whole thread Raw
In response to Re: explain analyze rows=%.0f  (Ibrar Ahmed <ibrar.ahmad@gmail.com>)
Responses Re: explain analyze rows=%.0f  (Ibrar Ahmed <ibrar.ahmad@gmail.com>)
List pgsql-hackers
On Wed, 4 Jan 2023 at 10:05, Ibrar Ahmed <ibrar.ahmad@gmail.com> wrote:
>
> Thanks, I have modified everything as suggested, except one point
>
> > Don't use variable format strings. They're hard to read and they
> > probably defeat compile-time checks that the arguments match the
> > format string. You could use a "*" field width instead, ie
...
> > * Another thought is that the non-text formats tend to prize output
> > consistency over readability, so maybe we should just always use 2
> > fractional digits there, rather than trying to minimize visible changes.
>
> In that, we need to adjust a lot of test case outputs.

> > * We need some doc adjustments, surely, to explain what the heck this
> > means.

That sounds like three points :) But they seem like pretty good
arguments to me and straightforward if a little tedious to adjust.

This patch was marked Returned with Feedback and then later Waiting on
Author. And it hasn't had any updates since January. What is the state
on this feedback? If it's already done we can set the patch to Ready
for Commit and if not do you disagree with the proposed changes?

It's actually the kind of code cleanup changes I'm reluctant to bump a
patch for. It's not like a committer can't make these kinds of changes
when committing. But there are so many patches they're likely to just
focus on a different patch when there are adjustments like this
pending.

-- 
Gregory Stark
As Commitfest Manager



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Question: Do we have a rule to use "PostgreSQL" and "PostgreSQL" separately?
Next
From: "Gregory Stark (as CFM)"
Date:
Subject: Re: Allow parallel plan for referential integrity checks?