From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Request - repeat value of \pset title during \watch interations |
Date: | 2016-01-11 11:14:10 |
Message-ID: | CAB7nPqRwP_bOZU9pUQ7G1xJ8SPdHf_BgtqHQxF_ehoqKtb7NYA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Mon, Jan 11, 2016 at 3:36 AM, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> When executing a query using \watch in psql the first execution of the query
> includes "Title is [...]" when \pset title is in use. Subsequent executions
> do not. Once that first display goes off-screen the information in the
> title is no longer readily accessible. If using \watch for a long-running
> monitoring query it can be helpful to incorporate some context information
> into the title.
Yeah, this sounds like a good idea to show it at each iteration if the
title is set. I am not sure we would want to treat that as a bug fix
as nothing is broken, it looks more like a new feature.
> Any suggestions for a better way to accomplish the goal?
What I have been doing in such cases until now is updating the name of
the terminal tab to identify what was going on.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Jones | 2016-01-11 12:39:04 | 9.4 -> 9.5 upgrade problem when both python2 and python3 present |
Previous Message | Oleksii Kliukin | 2016-01-11 10:55:44 | BDR: cascading setup |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2016-01-11 11:31:20 | Re: No Issue Tracker - Say it Ain't So! |
Previous Message | Simon Riggs | 2016-01-11 08:14:22 | Re: [COMMITTERS] pgsql: Avoid pin scan for replay of XLOG_BTREE_VACUUM |