Seperate command-line histories for seperate databases

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Seperate command-line histories for seperate databases
Date: 2006-03-17 16:20:43
Message-ID: 200603171720.43829.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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/

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-03-17 16:30:09 Re: Seperate command-line histories for seperate databases
Previous Message Marko Kreen 2006-03-17 15:50:45 Re: Commit turns into rollback?