Message-ID: <65ca67b5-932f-6d3e-554c-d66a3ab700a2@uni-muenster.de>
Date: Fri, 24 Feb 2023 13:09:47 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.7.1
Subject: Re: Proposal: :SQL_EXEC_TIME (like :ROW_COUNT) Variable (psql)
Content-Language: en-US, de-DE
To: Kirk Wolak <wolakk@gmail.com>, Maciek Sakrejda <m.sakrejda@gmail.com>
Cc: Nikolay Samokhvalov <samokhvalov@gmail.com>, Tom Lane
 <tgl@sss.pgh.pa.us>, Heikki Linnakangas <hlinnaka@iki.fi>,
 Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 Pavel Stehule <pavel.stehule@gmail.com>,
 Andrey Borodin <amborodin86@gmail.com>,
 Laurenz Albe <laurenz.albe@cybertec.at>
References: <CACLU5mSRwHr_8z=enMj-nXF1tmC7+Jn5heZQNiKuLyxYUtL2fg@mail.gmail.com>
 <157609.1677088525@sss.pgh.pa.us>
 <CANNMO+KqqM0YpVUmVDec+9nku9ai9T=Y5Tp=pZ0rp1jR3d8kqA@mail.gmail.com>
 <f4013949-746d-23e7-118d-6a7e9fa70c37@iki.fi>
 <2f1c8cb9-6f4d-2a03-d069-c4f9c2b574ab@enterprisedb.com>
 <e0320ffa-97ac-5976-ea76-2b9e87dd054c@iki.fi>
 <414445.1677163935@sss.pgh.pa.us>
 <CAOtHd0D28EgtwVKw+AUeEiH9Ai+-vUZH=PtCePBgpDp0WBY93Q@mail.gmail.com>
 <CANNMO++GPeo3v7DELX02stRqWcJGdAbkh3i04m5Vc5nC3kkHng@mail.gmail.com>
 <CAOtHd0B8+FHsNKVGy8Bg39MX31eg2UpTUd1NxexZgVvOs-WUaA@mail.gmail.com>
 <CACLU5mQKvCHUaCx_yooZJZ=Ud1Bddux48j7C2xF0cNQC8AqVQg@mail.gmail.com>
From: Jim Jones <jim.jones@uni-muenster.de>
In-Reply-To: <CACLU5mQKvCHUaCx_yooZJZ=Ud1Bddux48j7C2xF0cNQC8AqVQg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/65ca67b5-932f-6d3e-554c-d66a3ab700a2%40uni-muenster.de>
Precedence: bulk

On 23.02.23 20:55, Kirk Wolak wrote:
> Everyone,
>   I love that my proposal for %T in the prompt, triggered some great 
> conversations.
>
>   This is not instead of that.  That lets me run a query and come back 
> HOURS later, and know it finished before 7PM like it was supposed to!
>
>   This feature is simple.  We forget to set \timing on...
I've been there many times!
> We run a query, and we WONDER... how long did  that take.
>
>   This, too, should be a trivial problem (the code will tell).
>
>   I am proposing this to get feedback (I don't have a final design in 
> mind, but I will start by reviewing when and how ROW_COUNT gets set, 
> and what \timing reports).
>
>   Next up, as I learn (and make mistakes), this toughens me up...
>
>   I am not sure the name is right, but I would like to report it in 
> the same (ms) units as \timing, since there is an implicit 
> relationship in what they are doing.
>
>   I think like ROW_COUNT, it should not change because of internal 
> commands.
> So, you guys +1 this thing, give additional comments.  When the 
> feedback settles, I commit to making it happen.
>
> Thanks, Kirk
>
I can see it being pretty handy to check if a certain task involving two 
different terminal windows was done in the right order. Basically to see 
what went wrong, e.g. "did I really stop the master database before 
promoting the replica?"

+1 !

Best, Jim