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

From Bruce Momjian
Subject Re: Seperate command-line histories for seperate databases
Date
Msg-id 200603172135.k2HLZ3G28339@candle.pha.pa.us
Whole thread Raw
In response to Re: Seperate command-line histories for seperate databases  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
> > Chris Browne wrote:
> >> mbertheau.pg@googlemail.com ("Markus Bertheau") writes:
> >>> Any reason psql doesn't do this by default?
> >> 
> >> 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.
> 
> +1 on not changing the default behavior.  However, this discussion
> makes me wonder just how well the hack recommended by the psql man page
> actually works.  What happens if you use \c to change databases during
> a psql session?  What *should* happen, if you're trying to keep
> per-database histories?

Unless we re-read .psqlrc (which I don't think we do), we will dump into
the original file.

--  Bruce Momjian   http://candle.pha.pa.us SRA OSS, Inc.   http://www.sraoss.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Automatically setting work_mem
Next
From: Tom Lane
Date:
Subject: Re: Automatically setting work_mem