psql now shows zero elapsed time after an error - Mailing list pgsql-hackers

From Tom Lane
Subject psql now shows zero elapsed time after an error
Date
Msg-id 3813350.1652111765@sss.pgh.pa.us
Whole thread Raw
Responses Re: psql now shows zero elapsed time after an error
List pgsql-hackers
Example (you need up-to-the-minute HEAD for this particular test
case, but anything that runs a little while before failing will do):

regression=# \timing
Timing is on.
regression=# select * from generate_series('2022-01-01 00:00'::timestamptz,
                       'infinity'::timestamptz,
                       '1 month'::interval) limit 10;
ERROR:  timestamp out of range
Time: 0.000 ms

That timing is wrong.  It visibly takes more-or-less half a second
on my machine, and v14 psql reports that accurately:

regression=# \timing
Timing is on.
regression=# select * from generate_series('2022-01-01 00:00'::timestamptz,
                       'infinity'::timestamptz,
                       '1 month'::interval) limit 10;
ERROR:  timestamp out of range
Time: 662.107 ms

While I've not bisected, I think it's a dead cinch that 7844c9918
is what broke this.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: postgres_fdw "parallel_commit" docs
Next
From: Justin Pryzby
Date:
Subject: Re: postgres_fdw "parallel_commit" docs