Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\))
Subject: Re: explain analyze rows=%.0f
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <DBBD7E90-677A-4BF3-A5DD-B1A5D12F800C@yesql.se>
Date: Tue, 1 Aug 2023 22:29:05 +0200
Cc: "Gregory Stark (as CFM)" <stark.cfm@gmail.com>,
 Tom Lane <tgl@sss.pgh.pa.us>,
 Robert Haas <robertmhaas@gmail.com>,
 Amit Kapila <amit.kapila16@gmail.com>,
 Justin Pryzby <pryzby@telsasoft.com>,
 Peter Geoghegan <pg@bowt.ie>,
 vignesh C <vignesh21@gmail.com>,
 "David G. Johnston" <david.g.johnston@gmail.com>,
 pgsql-hackers@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A141D263-CA95-4873-BCC7-2573C908DAED@yesql.se>
References: <CA+TgmoZv8DvmeQHQAX+rkn68id2N+DoUhFZB36d-_w1tyAeqeA@mail.gmail.com>
 <20220707222015.GD13040@telsasoft.com>
 <CAA4eK1Lmo0FX6Nfr_k3-UX1Hpei1H-xPHL6Wwx7SLUP3s+O1mA@mail.gmail.com>
 <CA+Tgmob0BBeK6GEMUQBPiv0kJpTJSEgX+OUD2FeY42zWVgJuLw@mail.gmail.com>
 <2954811.1667711530@sss.pgh.pa.us>
 <CALtqXTfM3GJbFsB63ajfHcYvFhUA0ySX4f4MVS3Dau2vopU+Rw@mail.gmail.com>
 <CAM-w4HNLRO8QJvF3x13wjjdkJHobORxaKrcuyF1cKaTiXuvDbA@mail.gmail.com>
 <CALtqXTcZE6YW=m9ZmNU6sRJ+RTC15NFc__foP1S2KaWvGOf6JA@mail.gmail.com>
 <DBBD7E90-677A-4BF3-A5DD-B1A5D12F800C@yesql.se>
To: Ibrar Ahmed <ibrar.ahmad@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/A141D263-CA95-4873-BCC7-2573C908DAED%40yesql.se>
Precedence: bulk

> On 3 Jul 2023, at 18:34, Daniel Gustafsson <daniel@yesql.se> wrote:
>=20
>> On 8 Jun 2023, at 19:49, Ibrar Ahmed <ibrar.ahmad@gmail.com> wrote:
>> On Mon, Mar 20, 2023 at 7:56=E2=80=AFPM Gregory Stark (as CFM) =
<stark.cfm@gmail.com <mailto:stark.cfm@gmail.com>> wrote:
>=20
>> 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?
>>=20
>> If there is a consensus to modify the test cases' output, I am =
willing to
>> make the necessary changes and adjust the patch accordingly. However,
>> if there is a preference to keep the output of certain test cases =
unchanged,
>> I can rebase and modify the patch accordingly to accommodate those =
preferences.
>=20
> As there hasn't been any other comments I suggest updating your patch =
to
> address Tom's comments to see if we can make progress here.

Since there hasn't been any updates here, and the thread has been =
stalled, I'm
marking this returned with feedback.  Please feel free to resubmit a =
version of
the patch addressing comments to a future CF.

--
Daniel Gustafsson