On Tue, Oct 18, 2016 at 9:26 AM, Jonathan Jacobson <jonjac@gmail.com> wrote:
The .psql_history file is naturally used by different DB connections (distinguished by a different combination of host + port + database + user).
At least in my multi-database working environment, this leads sometimes to frustration because there are commands that cannot or should not be used by different connections.
To solve this, psql could keep a separate command history file for each connection.
I will be happy to make this my first contribution to PostgreSQL's code.
What do you say?
I would say that users needing such fine grained control of the history file should avail themselves of HISTFILE and other related psql variables and/or the PSQL_HISTORY environment variable.
