From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | David Christensen <david(at)endpoint(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Explicit psqlrc |
Date: | 2010-03-05 09:39:09 |
Message-ID: | 9837222c1003050139p671e8b44i11adefb09a51c442@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/3/5 David Christensen <david(at)endpoint(dot)com>:
>
> On Mar 4, 2010, at 4:00 PM, Magnus Hagander wrote:
>
>> I've now for the second time found myself wanting to specify an
>> explicit psqlrc file instead of just parsing ~/.psqlrc, so attached is
>> a patch that accepts the PSQLRC environment variable to control which
>> psqlrc file is used.
>>
>> Any objections to this (obviously including documentation - this is
>> just the trivial code)
>
>
> My bikeshed has a --psqlrc path/to/file, but +1 on the idea.
The main reason I went with environment variable is that it's the
path-of-least-code :-) And it easily fullfills my use-cases for it,
which has me launching interactive psql with completely different
settings from a script.
Do you have a use-case where --psqlrc would be more useful than an
environment variable, or is it *only* bike-shedding? ;)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Jesper Krogh | 2010-03-05 09:46:39 | Using GIN/Gist to search the "union" of two indexes? |
Previous Message | Dave Page | 2010-03-05 09:37:25 | Re: Visual Studio 2005, C-language function - avoiding hacks? |