Seperate command-line histories for seperate databases - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Seperate command-line histories for seperate databases
Date
Msg-id 200603171720.43829.peter_e@gmx.net
Whole thread Raw
Responses Re: Seperate command-line histories for seperate databases  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
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, especially since the new history from db2 is probably
not useful for db1.

I'd suggest giving psql a directory, and naming history like this:
       .psql/history/hostname/dbname
"""

There is undoubtedly some merit to that, but I still have my doubts.  But at 
least we can discuss it.  Comments?

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


pgsql-hackers by date:

Previous
From: "Marko Kreen"
Date:
Subject: Re: Commit turns into rollback?
Next
From: Bruce Momjian
Date:
Subject: Re: Seperate command-line histories for seperate databases