Re: location of the configuration files
От | Dave Page |
---|---|
Тема | Re: location of the configuration files |
Дата | |
Msg-id | 03AF4E498C591348A42FC93DEA9661B8259C59@mail.vale-housing.co.uk обсуждение исходный текст |
Ответ на | location of the configuration files (mlw <pgsql@mohawksoft.com>) |
Список | pgsql-hackers |
> -----Original Message----- > From: Christopher Browne [mailto:cbbrowne@acm.org] > Sent: 13 February 2003 13:33 > To: pgsql-hackers@postgresql.org > Subject: Re: [HACKERS] location of the configuration files > > > In the last exciting episode, cjs@cynic.net (Curt Sampson) wrote: > > On Wed, 12 Feb 2003, Peter Bierman wrote: > > > >> What do you gain by having the postmaster config and the database > >> data live in different locations? > > > > You can then standardize a location for the configuration files. > > > > Everybody has room in /etc for another 10K of data. Where you have > > room for something that might potentially be a half > terrabyte of data, > > and is not infrequently several gigabytes or more, is pretty > > system-depenendent. > > Ah, but this has two notable problems: > > 1. It assumes that there is "a location" for "the configuration files > for /the single database instance./" > > If I have a second database instance, that may conflict. > > 2. It assumes I have write access to /etc > > If I'm a Plain Old User, as opposed to root, I may only have > read-only access to /etc. > > These conditions have both been known to occur... So we can presumably allow the location to be overridden with a configure option? Regards, Dave
В списке pgsql-hackers по дате отправления: