| From: | Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com> |
|---|---|
| To: | Jonathan Jacobson <jonjac(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Multiple psql history files |
| Date: | 2016-10-18 16:33:39 |
| Message-ID: | 9da2d8ca-2f4c-97f1-bc07-d5e875e0c50f@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18/10/2016 18:26, Jonathan Jacobson 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.
You can already do this, for instance in your .psqlrc:
\set HISTFILE ~/.psql_history- :HOST - :PORT - :DBNAME - :USER
--
Julien Rouhaud
http://dalibo.com - http://dalibo.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-10-18 16:43:29 | Re: Multiple psql history files |
| Previous Message | David G. Johnston | 2016-10-18 16:32:53 | Re: Multiple psql history files |