Re: Seperate command-line histories for seperate databases

Поиск
Список
Период
Сортировка
От Darcy Buskermolen
Тема Re: Seperate command-line histories for seperate databases
Дата
Msg-id 200603171428.32265.darcy@wavefire.com
обсуждение исходный текст
Ответ на Re: Seperate command-line histories for seperate databases  (Chris Browne <cbbrowne@acm.org>)
Список pgsql-hackers
On Friday 17 March 2006 10:55, 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...

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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Automatically setting work_mem
Следующее
От: Martijn van Oosterhout
Дата:
Сообщение: Re: Automatically setting work_mem