On Tue, Oct 18, 2016 at 10:21 AM, Tom Lane wrote:
> "David G. Johnston" writes:
> > On Tue, Oct 18, 2016 at 9:45 AM, Tom Lane wrote:
> >> One interesting point, if you wish to consider history as being
> >> connection-specific, is what happens during a \c command. Right
> >> now the answer is
"David G. Johnston" writes:
> On Tue, Oct 18, 2016 at 9:45 AM, Tom Lane wrote:
>> One interesting point, if you wish to consider history as being
>> connection-specific, is what happens during a \c command. Right
>> now the answer is "nothing" but you might wish it were different.
> ​Just to cl
On Tue, Oct 18, 2016 at 9:45 AM, Tom Lane wrote:
> Jonathan Jacobson writes:
> > 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 lea
Jonathan Jacobson writes:
> 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
On Tue, Oct 18, 2016 at 9:26 AM, 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
> frustratio
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 ther
On Tue, Oct 18, 2016 at 9:26 AM, 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
> frustratio
On Tue, Oct 18, 2016 at 12:26 PM, 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
> frustrati
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
di
