Re: Explicit psqlrc
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: David Christensen <david@endpoint.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-03-05T10:30:22Z
Lists: pgsql-hackers
Attachments
- psqlrc.patch (application/octet-stream) patch
2010/3/5 Magnus Hagander <magnus@hagander.net>: > 2010/3/5 David Christensen <david@endpoint.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? ;) Just to be clear, the code difference isn't very large. Attached is a patch that does both PSQLRC and --psqlrc. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/