Re: Seperate command-line histories for seperate databases

Bruce Momjian <pgman@candle.pha.pa.us>

From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>, Chris Browne <cbbrowne@acm.org>, pgsql-hackers@postgresql.org
Date: 2006-03-17T21:35:03Z
Lists: 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. +