Re: Seperate command-line histories for seperate databases - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Seperate command-line histories for seperate databases
Date
Msg-id 441B0A90.3080505@dunslane.net
Whole thread Raw
In response to Re: Seperate command-line histories for seperate databases  (Chris Browne <cbbrowne@acm.org>)
Responses Re: Seperate command-line histories for seperate databases
List pgsql-hackers
Chris Browne wrote:

>mbertheau.pg@googlemail.com ("Markus Bertheau") writes:
>  
>
>>2006/3/17, Bruce Momjian <pgman@candle.pha.pa.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


pgsql-hackers by date:

Previous
From: Chris Browne
Date:
Subject: Re: Seperate command-line histories for seperate databases
Next
From: Josh Berkus
Date:
Subject: Re: Automatically setting work_mem