From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Reporting script runtimes in pg_regress
In-reply-to: <E7790843-B885-492B-8537-CC9FB39D5F97@yesql.se>
References: <16646.1549770618@sss.pgh.pa.us>
 <E7790843-B885-492B-8537-CC9FB39D5F97@yesql.se>
Comments: In-reply-to Daniel Gustafsson <daniel@yesql.se>
	message dated "Sun, 10 Feb 2019 22:21:27 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <11412.1549835730.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 10 Feb 2019 16:55:30 -0500
Message-ID: <11413.1549835730@sss.pgh.pa.us>
Precedence: bulk

Daniel Gustafsson <daniel@yesql.se> writes:
>> On 10 Feb 2019, at 04:50, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Does anyone else feel that this is interesting/useful data?

> Absolutely, +1 on this.  In Greenplum we print the runtime of the script=
 and
> the runtime of the diff, both of which have provided useful feedback on =
where
> to best spend optimization efforts (the diff time of course being a lot =
less
> interesting in upstream postgres due to gpdb having it=E2=80=99s own dif=
f tool to
> handle segment variability).

Seems like I'm far from the first to think of this --- I wonder why
nobody submitted a patch before?

Anyway, pushed.

			regards, tom lane