Re: Seperate command-line histories for seperate databases

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Seperate command-line histories for seperate databases
Date: 2006-03-17 20:27:36
Message-ID: 9823.1142627256@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Chris Browne wrote:
>> mbertheau(dot)pg(at)googlemail(dot)com ("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 *same*
>> queries to them.
>>
>> This change would make it troublesome to do that. I'd not be all that
>> keen on the change...

> Just what I was thinking.

+1 on not changing the default behavior. However, this discussion
makes me wonder just how well the hack recommended by the psql man page
actually works. What happens if you use \c to change databases during
a psql session? What *should* happen, if you're trying to keep
per-database histories?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2006-03-17 21:07:37 Re: Automatically setting work_mem
Previous Message Tom Lane 2006-03-17 20:18:14 Re: Automatically setting work_mem