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:43:29 |
Message-ID: | CAKFQuwYzcEoSuTurjs2MzCrZeK2kh1XW3TrcnCUWFyisse5EZQ@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?
>
>
Existing capabilities not withstanding the feature itself would probably
be considered but I'm doubtful it would replace the default behavior.
The user would, at minimum, have to designate
a directory into which the separate history files would be created -
polluting the home directory is unappealing.
If you want to propose the specifics of a feature that meets those two
criteria specific comments and opinions on include-ability can be made.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-10-18 16:45:20 | Re: Multiple psql history files |
Previous Message | Julien Rouhaud | 2016-10-18 16:33:39 | Re: Multiple psql history files |