From: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: alternate psql file locations |
Date: | 2011-12-31 21:26:19 |
Message-ID: | CAC_2qU9K8UGDDVjA_DcCMVsca4379aY7DaPeT8-56MgJ3QT1Sg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Dec 31, 2011 at 3:17 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
>
> Excerpts from Andrew Dunstan's message of sáb dic 31 12:52:02 -0300 2011:
>> It's not a big thing, but I just found myself in a shared environment
>> wanting to be able to set alternative locations for the psql startup
>> file and history. I know there's the HISTFILE variable, but I can't
>> easily set that automatically unless I can at least have my own .psqlrc.
>> ISTM it should be a fairly simple thing to provide these, via
>> environment variables. Is there general interest in such a thing?
>
> I wanted such a thing mere two weeks ago ...
Generally when I've wanted these things, I just make a new "$HOME" in
my shared user home dir:
export HOME=$HOME/aidan
It's worked for things I've wanted, I haven't tried it for psql stuff....
a.
--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.
From | Date | Subject | |
---|---|---|---|
Next Message | Brar Piening | 2011-12-31 23:10:26 | Re: Review of VS 2010 support patches |
Previous Message | Alvaro Herrera | 2011-12-31 20:17:59 | Re: alternate psql file locations |