Re: PSQLRC environment variable. - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: PSQLRC environment variable.
Date
Msg-id 200403101612.i2AGCQl10721@candle.pha.pa.us
Whole thread Raw
In response to Re: PSQLRC environment variable.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PSQLRC environment variable.
List pgsql-patches
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Tom Lane wrote:
> >> Uh, why is that a good idea?
>
> > Well, suppose you want all your users to use the same psqlrc file.
> > Instead of creating symlinks for every user, you can just set PSQLRC in
> > /etc/profile and everyone gets it.
>
> ... but people who want to make their own .psqlrc can't?  At least not
> till it occurs to them to unset PSQLRC?  I don't really see the use-case
> here.  James' stated problem of setting a default search_path could be

If they want their own, the just unset PSQLRC in their .profile.

> handled at least as effectively through either PGOPTIONS or server-side
> GUC settings (postgresql.conf, or per-user or per-database variable
> settings).
>
> I'm not averse to inventing PSQLRC if there's actually some case it
> solves better than any of our existing mechanisms.  But so far it seems
> like a solution desperately in search of a problem.

I think most/all applications that look for a file in the user directory
have either a global place they look too, or a way to control where to
look for it.  This seems pretty Unix standard, I think we should follow
that.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Initial Review of Copy Command Patch
Next
From: Andrew Dunstan
Date:
Subject: remove log_timestamp, log_pid and log_source_port GUC vars