Re: What is the motivation of include directive and
От | Takayuki Tsunakawa |
---|---|
Тема | Re: What is the motivation of include directive and |
Дата | |
Msg-id | 01c201c739f6$fc1ebf40$19527c0a@OPERAO обсуждение исходный текст |
Ответ на | Re: What is the motivation of include directive and (Bruce Momjian <bruce@momjian.us>) |
Список | pgsql-hackers |
From: "Tom Lane" <tgl@sss.pgh.pa.us> > "Takayuki Tsunakawa" <tsunakawa.takay@jp.fujitsu.com> writes: >> Still, I don't understand well why config files need to be placed >> outside the data directory, except for daring conform to FHS. > > The killer argument for it is that most of what is in $PGDATA should be > excluded from your normal filesystem backup method, because you need to > be using some database-aware mechanism for backing up the database. But > the config files are perfectly suited for standard filesystem backup, > and indeed will *not* be covered by, say, pg_dumpall. So putting them > somewhere else helps in creating a coherent backup strategy. Thank you, I've understood the reason for placement. As I supposed, it is provided mainly for placing config files in /etc to allow frequent backup of the configuration as a whole system, because most config files of UNIX are stored in /etc (recommended so in FHS) and /etc is small.
В списке pgsql-hackers по дате отправления: