Re: Multiple psql history files

Поиск
Список
Период
Сортировка
От Corey Huinker
Тема Re: Multiple psql history files
Дата
Msg-id CADkLM=f1pkL4YXiM8GR+23ohtktuwaiL0gQJK3WBxTmV6+jw8w@mail.gmail.com
обсуждение исходный текст
Ответ на Multiple psql history files  (Jonathan Jacobson <jonjac@gmail.com>)
Список pgsql-hackers
Дерево обсуждения
On Tue, Oct 18, 2016 at 12:26 PM, 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?

Regards,
Jonathan

That's settable with HISTFILE

\set HISTFILE ~/.psql_history- :DBNAME

There's also :PORT and a few other vars. 

(example borrowed from http://stackoverflow.com/questions/17924906/where-is-psql-client-history-kept-psql-history-non-existant)


В списке pgsql-hackers по дате отправления: