From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | James Tanis <jtt(at)sysd(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: PSQLRC environment variable. |
Date: | 2004-03-14 05:05:33 |
Message-ID: | 18343.1079240733@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I just checked a few apps and I see they usually allow a global config
> file to be specified. How about SYSPSQLRC that adds a system-wide psql
> config file to be read before the one in the home directory?
The ones I know of that allow such a thing generally hard-wire the
location of the global config file at build time, rather than taking it
from an environment variable. The env var approach seems weird, and a
tad inefficient (since you'd have to put such an env var into the global
.profile, meaning it propagates into every single process ever launched
on your system). Also I think we have at least one global config file
already for libpq, and its location is hard-wired.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Natoli | 2004-03-14 05:36:48 | misc patches (minor) |
Previous Message | Tom Lane | 2004-03-14 04:33:04 | Re: client side syntax error position (v3) |