Re: Proposal: %T Prompt parameter for psql for current time (like Oracle has)

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kirk Wolak <wolakk(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, amborodin86(at)gmail(dot)com, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Subject: Re: Proposal: %T Prompt parameter for psql for current time (like Oracle has)
Date: 2023-02-23 11:20:23
Message-ID: 2f1c8cb9-6f4d-2a03-d069-c4f9c2b574ab@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22.02.23 19:14, Heikki Linnakangas wrote:
> How about a new backslash command or psql variable to show how long the
> previous statement took? Something like:

If you don't have \timing turned on before the query starts, psql won't
record what the time was before the query, so you can't compute the run
time afterwards. This kind of feature would only work if you always
take the start time, even if \timing is turned off.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2023-02-23 11:27:23 Re: buildfarm + meson
Previous Message Peter Eisentraut 2023-02-23 11:07:58 Re: some namespace.c refactoring