Re: initdb: directory not empty issue

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: initdb: directory not empty issue
Дата
Msg-id 23371.1075510611@sss.pgh.pa.us
обсуждение исходный текст
Ответ на initdb: directory not empty issue  (Jeffrey Quinn <jquinn@cs.usfca.edu>)
Список pgsql-bugs
Jeffrey Quinn <jquinn@cs.usfca.edu> writes:
> The problem, however, is that this will fail if I am trying to enable a
> separate filesystem as the data location.  It's rather annoying to have
> to remove a lost+found directory (or other files), init the db, and then
> remake lost+found (and restore other files).  How about a --force
> flag?

Why not create a /data directory just below the filesystem root, and use
that?

I believe it's generally considered that root should own filesystem
mount points, so using a filesystem root directory directly as the PG
data directory seems like bad practice.

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Kris Jurka
Дата:
Сообщение: Re: Why not (OID) in JDeveloper10g?
Следующее
От: yogesh selukar
Дата:
Сообщение: pg_dump: procedural language for function fun_update_tptype_master not found