Marc G. Fournier wrote:
>
> On Fri, 20 Jun 1997, Vadim B. Mikheev wrote:
>
> > Marc G. Fournier wrote:
> > >
> > > 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...
>
...
>
> My vote is in favor of a pg_profile table *instead of* flat files
^^^^^^^^^^^^
We may add both features and let ppl to decide what to use.
pg_profile will be processed by backend before any commands from client
and so .pgsqlrc (or like one) may overwrite default settings for user.
> in the users directory. When createdb is run, have a 'system default'
> profile written to that databases pg_profile? Or would each table created
^^^^
Why not in .../data dirrectory ? User may connect to different databases...
...But - it requires dump/reload...
.pgsqlrc doesn't...
Vadim
------------------------------
