Re: Seperate command-line histories for seperate databases

From: Darcy Buskermolen <darcy(at)wavefire(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Chris Browne <cbbrowne(at)acm(dot)org>
Subject: Re: Seperate command-line histories for seperate databases
Date: 2006-03-17 22:28:31
Message-ID: 200603171428.32265.darcy@wavefire.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Friday 17 March 2006 10:55, 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...

I'm with Chris on this one, I routinly execute the same command on 6 or 7 of
our databases, all from the same management consol. I would find a change
of this sort soemewhat frustrating, I'd probably be inclined to symlink all
my history files together. The presented way looks perfectly acceptable to
me.

--
Darcy Buskermolen
Wavefire Technologies Corp.

http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-03-17 22:29:34 Re: Automatically setting work_mem
Previous Message Tom Lane 2006-03-17 21:45:17 Re: Automatically setting work_mem