Re: registry vs. environment (was re:binary
От | Bruce Momjian |
---|---|
Тема | Re: registry vs. environment (was re:binary |
Дата | |
Msg-id | 200402121747.i1CHlBY22021@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: registry vs. environment (was re:binary (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: registry vs. environment (was re:binary
|
Список | pgsql-hackers-win32 |
Andrew Dunstan wrote: > >The win32 TODO now has: > > > > Store settings in the registry and set environment variables in > > the process > > > >What additional things to we need to deal with if we go the direction of > >having the environment variables set from the registry and read-only in > >the process? > > > > > > > > I'm not clear *which* settings it is proposed to set in the registry, > nor how possible it will be to override the settings, and with which > mechanism. I assumed all environment variables would be exported to the process. The problem is allowing environment variables to override registry settings. One idea would be to do both --- if an environment variable isn't set, get the value from the registry and set the envronment variable. If the environment variable is set, use that instead of the registry --- that might be the best of both worlds. > The nicest things might be those things like paths that we currently set > at configure time - making postgres more easily relocatable would be a > Good Thing (tm). > > We need to ensure that using the registry still allows us to run > multiple instances and multiple installations on the same machine easily. Yes, I think the above idea would work for 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-hackers-win32 по дате отправления: