From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Jonathan Jacobson <jonjac(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Multiple psql history files |
Date: | 2016-10-18 17:21:38 |
Message-ID: | 23615.1476811298@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Tue, Oct 18, 2016 at 9:45 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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 clarify/confirm a point inferred from the docs...
> If you place "\set HISTFILE ~/.psql_history- :DBNAME"
> into your .psqlrc file then when you perform a "\c" the .psqlrc file is
> re-read and the new value for DBNAME is used to generate a new history
> file name.
Um, no, I see no indication of that in the code. Where did you read that
in the docs?
If we wanted the history file to change at \c, I think the best way would
be to invent some escape-patterns that could be placed in the value of
HISTFILE, say along the lines of "\set HISTFILE ~/.psql_history-%h-%p",
and then specify that if the value contains any such patterns we'll dump
and reload the history file when reconnecting. But TBH I don't think
it's worth the trouble. I'd sure like to have seen multiple requests
for such functionality before we go to the trouble.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-10-18 17:22:59 | Re: Hash Indexes |
Previous Message | David G. Johnston | 2016-10-18 16:56:27 | Re: Multiple psql history files |