On Fri, 20 Jun 1997, Vadim B. Mikheev wrote:
> Marc G. Fournier wrote:
> >
> > On Fri, 20 Jun 1997, Martin J. Laubach wrote:
> >
> > > > for psql to read ~/.psqlrc (or some such thing) as a set of
> > >
> > > psql already takes some environment variables and sends them
> > > to the server. In fact, libpq does that. I think it is called
> > > PG_DATE or such? (Hmm, maybe I should have documented it somewhere :)
> >
> > IMHO, a .psqlrc file would be easier overall...should even have
> > some sort of 'global' one, maybe? Or maybe use env variables for global
> > settings, to be overwritten by a psqlrc?
>
> IMHO, 'global' one is fine idea. It may be used by different
> applications and proccessed by libpq on startup automatically.
> After 'global' is proccessed additional commands from .psqlrc
> may be posted to backend as well...
>
> What about user profiles stored in database in system pg_profile
> table ? We live in virtual world...
I'd think that would be the optimal way to do it, myself...if I
backup the database server to a tape, I'm not going to add in each individual
users .psqlrc files, but if that information is stored in a pg_profile file,
then it automagically gets backed up...
My vote is in favor of a pg_profile table *instead of* flat files
in the users directory. When createdb is run, have a 'system default'
profile written to that databases pg_profile? Or would each table created
have a 'profile'?
Marc G. Fournier scrappy@hub.org
Systems Administrator @ hub.org scrappy@freebsd.org
------------------------------
