From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Takayuki Tsunakawa" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: What is the motivation of include directive and |
Date: | 2007-01-17 04:50:31 |
Message-ID: | 4684.1169009431@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Takayuki Tsunakawa" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Takayuki Tsunakawa | 2007-01-17 05:18:55 | Re: What is the motivation of include directive and |
Previous Message | Takayuki Tsunakawa | 2007-01-17 04:41:02 | Re: What is the motivation of include directive and |