| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jonathan Jacobson <jonjac(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Multiple psql history files |
| Date: | 2016-10-18 16:32:53 |
| Message-ID: | CAKFQuwaWsvY84ygvD0pcOZKNTTzXriYVRLS1fu=K6yT25nxZGg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 18, 2016 at 9:26 AM, Jonathan Jacobson <jonjac(at)gmail(dot)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.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2016-10-18 16:33:39 | Re: Multiple psql history files |
| Previous Message | Corey Huinker | 2016-10-18 16:32:22 | Re: Multiple psql history files |