public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jim Jones <[email protected]>
To: Kirk Wolak <[email protected]>
To: Maciek Sakrejda <[email protected]>
Cc: Nikolay Samokhvalov <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: Pavel Stehule <[email protected]>
Cc: Andrey Borodin <[email protected]>
Cc: Laurenz Albe <[email protected]>
Subject: Re: Proposal: :SQL_EXEC_TIME (like :ROW_COUNT) Variable (psql)
Date: Fri, 24 Feb 2023 13:09:47 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CACLU5mQKvCHUaCx_yooZJZ=Ud1Bddux48j7C2xF0cNQC8AqVQg@mail.gmail.com>
References: <CACLU5mSRwHr_8z=enMj-nXF1tmC7+Jn5heZQNiKuLyxYUtL2fg@mail.gmail.com>
	<[email protected]>
	<CANNMO+KqqM0YpVUmVDec+9nku9ai9T=Y5Tp=pZ0rp1jR3d8kqA@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAOtHd0D28EgtwVKw+AUeEiH9Ai+-vUZH=PtCePBgpDp0WBY93Q@mail.gmail.com>
	<CANNMO++GPeo3v7DELX02stRqWcJGdAbkh3i04m5Vc5nC3kkHng@mail.gmail.com>
	<CAOtHd0B8+FHsNKVGy8Bg39MX31eg2UpTUd1NxexZgVvOs-WUaA@mail.gmail.com>
	<CACLU5mQKvCHUaCx_yooZJZ=Ud1Bddux48j7C2xF0cNQC8AqVQg@mail.gmail.com>

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

view thread (18+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Proposal: :SQL_EXEC_TIME (like :ROW_COUNT) Variable (psql)
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox