Re: Patch to psql to allow SEARCH_PATH to be set from env
От | Tom Lane |
---|---|
Тема | Re: Patch to psql to allow SEARCH_PATH to be set from env |
Дата | |
Msg-id | 14955.1076427008@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Patch to psql to allow SEARCH_PATH to be set from env (Christopher Kings-Lynne <chriskl@familyhealth.com.au>) |
Ответы |
Re: Patch to psql to allow SEARCH_PATH to be set from env
|
Список | pgsql-patches |
Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes: > Do you know that you can go ALTER USER yourselft SET SEARCH_PATH TO > "'public','core','objects'"; So that will always be your default path? Another possibility is to issue the SET from a ~/.psqlrc file (I think that's what it's called, check the man page). It makes sense to support environment variables for connection parameters, since those can't be gotten from the database (for obvious reasons) nor from ~/.psqlrc (which isn't read till after connecting). But I'm not eager to support environment variables for things that can be set those ways. There are a heck of a lot of SET variables --- would we want an env var for each one? (Seen in this light, PGCLIENTENCODING is a wart, but I suppose we have to keep it for backwards compatibility.) regards, tom lane
В списке pgsql-patches по дате отправления: