Re: Seperate command-line histories for seperate databases
От | Chris Browne |
---|---|
Тема | Re: Seperate command-line histories for seperate databases |
Дата | |
Msg-id | 60y7z8vr3u.fsf@dba2.int.libertyrms.com обсуждение исходный текст |
Ответ на | Re: Seperate command-line histories for seperate databases (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: Seperate command-line histories for seperate databases
Re: Seperate command-line histories for seperate databases |
Список | pgsql-hackers |
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... -- select 'cbbrowne' || '@' || 'ntlug.org'; http://cbbrowne.com/info/rdbms.html "On the other hand, O'Reilly's book about running W95 has a toad as the cover animal. Makes sense; both have lots of warts and croak all the time." --- Michael Kagalenko,
В списке pgsql-hackers по дате отправления: