Re: Seperate command-line histories for seperate databases

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Seperate command-line histories for seperate databases
Date: 2006-03-17 21:35:03
Message-ID: 200603172135.k2HLZ3G28339@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > Chris Browne wrote:
> >> mbertheau(dot)pg(at)googlemail(dot)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. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-03-17 21:45:17 Re: Automatically setting work_mem
Previous Message Hannu Krosing 2006-03-17 21:07:37 Re: Automatically setting work_mem