| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Can we automatically add elapsed times to tap test log? |
| Date: | 2022-04-07 23:55:11 |
| Message-ID: | 014bb7f5-04c4-ae36-1cf6-a462634f8a9b@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/7/22 17:58, Andres Freund wrote:
> Hi,
>
> On 2022-04-07 17:45:09 -0400, Tom Lane wrote:
>> Andres Freund <andres(at)anarazel(dot)de> writes:
>>> On 2022-04-07 17:21:09 -0400, Tom Lane wrote:
>>>> I too think that the elapsed time is useful. I'm less convinced
>>>> that the time-of-day marker is useful.
>>> I think it'd be quite useful if it had more precision - it's a pita to
>>> correlate regress_log_* output with server logs.
>> Fair point. Maybe we could keep the timestamp (with ms precision
>> if possible) and then the parenthetical bit is time-since-last-line
>> (also with ms precision)? I think that would more or less satisfy
>> both uses.
> Would work for me...
>
All doable. Time::HiRes gives us a higher resolution timer. I'll post a
new version in a day or two.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-04-07 23:59:31 | Re: why pg_walfile_name() cannot be executed during recovery? |
| Previous Message | Tom Lane | 2022-04-07 23:52:19 | Re: API stability [was: pgsql: Fix possible recovery trouble if TRUNCATE overlaps a checkpoint.] |