| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
| Cc: | Philipp Gramzow <phil(at)philphonic(dot)de>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: incoorect restore_command |
| Date: | 2021-02-25 06:54:54 |
| Message-ID: | YDdJvgQIiBcF6JgR@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, Feb 24, 2021 at 08:15:59PM +0900, Fujii Masao wrote:
> But I have one question; why do those commands use different
> archive directories? Isn't it better to use the same one?
storage.sgml uses /var/lib/pgsql/data for the location of the data,
and the archive path is a mix between /mnt/server/archivedir/ and
/var/lib/pgsql/archive/. However, the former is used for
pg_archivecleanup and in postgresql.conf.sample, so why not just using
/mnt/server/archivedir/ in backup.sgml? Please see the attached.
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| doc-archive-gz-v2.patch | text/x-diff | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-02-25 07:09:31 | Re: pgbench: supports PGDATABASE / warning about -d |
| Previous Message | Michael Paquier | 2021-02-25 02:41:47 | Re: Inaccuracy in wal_receiver_status_interval parameter description |