From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Chris Browne <cbbrowne(at)acm(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Seperate command-line histories for seperate databases |
Date: | 2006-03-17 19:14:24 |
Message-ID: | 441B0A90.3080505@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Chris Browne wrote:
>mbertheau(dot)pg(at)googlemail(dot)com ("Markus Bertheau") writes:
>
>
>>2006/3/17, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>:
>>
>>
>>>Peter Eisentraut wrote:
>>>
>>>
>>>>Bruce Momjian wrote:
>>>>
>>>>
>>>>>The psql manual pages for 8.1 now has:
>>>>>
>>>>>
>>>>> \set HISTFILE ~/.psql_history- :DBNAME
>>>>>
>>>>>
>>Any reason psql doesn't do this by default? It is clear that the
>>database name does not unambiguously identify a database, but having a
>>history for each database name is already an improvement over the
>>current situation.
>>
>>
>
>I fairly frequently find myself accessing different (but similar)
>databases, and it's quite valuable to be able to submit the *same*
>queries to them.
>
>This change would make it troublesome to do that. I'd not be all that
>keen on the change...
>
>
Just what I was thinking.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2006-03-17 19:16:02 | Re: Automatically setting work_mem |
Previous Message | Chris Browne | 2006-03-17 18:55:01 | Re: Seperate command-line histories for seperate databases |