Re: [HACKERS] Seperate command-line histories for seperate databases

2006-03-17 Thread Darcy Buskermolen
On Friday 17 March 2006 10:55, Chris Browne wrote: > [EMAIL PROTECTED] ("Markus Bertheau") writes: > > 2006/3/17, Bruce Momjian : > >> Peter Eisentraut wrote: > >> > Bruce Momjian wrote: > >> > > The psql manual pages for 8.1 now has: > >> > > > >> > > \set HISTFILE ~/.psql_history- :

Re: [HACKERS] Seperate command-line histories for seperate databases

2006-03-17 Thread Bruce Momjian
Tom Lane wrote: > Andrew Dunstan <[EMAIL PROTECTED]> writes: > > Chris Browne wrote: > >> [EMAIL PROTECTED] ("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 valua

Re: [HACKERS] Seperate command-line histories for seperate databases

2006-03-17 Thread Tom Lane
Andrew Dunstan <[EMAIL PROTECTED]> writes: > Chris Browne wrote: >> [EMAIL PROTECTED] ("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 *

Re: [HACKERS] Seperate command-line histories for seperate databases

2006-03-17 Thread Andrew Dunstan
Chris Browne wrote: [EMAIL PROTECTED] ("Markus Bertheau") writes: 2006/3/17, Bruce Momjian : Peter Eisentraut wrote: Bruce Momjian wrote: The psql manual pages for 8.1 now has: \set HISTFILE ~/.psql_history- :DBNAME Any reason psql

Re: [HACKERS] Seperate command-line histories for seperate databases

2006-03-17 Thread Chris Browne
[EMAIL PROTECTED] ("Markus Bertheau") writes: > 2006/3/17, Bruce Momjian : >> 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

Re: [HACKERS] Seperate command-line histories for seperate databases

2006-03-17 Thread Bruce Momjian
Markus Bertheau wrote: > 2006/3/17, Bruce Momjian : > > 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 > databa

Re: [HACKERS] Seperate command-line histories for seperate databases

2006-03-17 Thread Markus Bertheau
2006/3/17, Bruce Momjian : > 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

Re: [HACKERS] Seperate command-line histories for seperate databases

2006-03-17 Thread Bruce Momjian
Peter Eisentraut wrote: > Bruce Momjian wrote: > > The psql manual pages for 8.1 now has: > > > \set HISTFILE ~/.psql_history- :DBNAME > > Excellent! Yea, it is a cool trick someone posted once and I added it to the manual page for others to use. -- Bruce Momjian http://candl

Re: [HACKERS] Seperate command-line histories for seperate databases

2006-03-17 Thread Peter Eisentraut
Bruce Momjian wrote: > The psql manual pages for 8.1 now has: > \set HISTFILE ~/.psql_history- :DBNAME Excellent! -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 9: In versions below 8.0, th

Re: [HACKERS] Seperate command-line histories for seperate databases

2006-03-17 Thread Bruce Momjian
Peter Eisentraut wrote: > Someone sent the following request to the Debian bug tracking system: > > """ > It'd be nice if the .psql_history file were per-database. This is > because the commands executed on different databases are likely to be > very different, so there is no good reason to lose h

[HACKERS] Seperate command-line histories for seperate databases

2006-03-17 Thread Peter Eisentraut
Someone sent the following request to the Debian bug tracking system: """ It'd be nice if the .psql_history file were per-database. This is because the commands executed on different databases are likely to be very different, so there is no good reason to lose history for db1 when working with db2