| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | phil(at)philphonic(dot)de, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: incoorect restore_command |
| Date: | 2021-02-24 05:49:14 |
| Message-ID: | YDXo2tIJmkW6mhkm@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Feb 22, 2021 at 07:36:28AM +0000, PG Doc comments form wrote:
> I've been trying out saving and restoring compressed archive logs. The
> restore_command stated in the docs at "25.3.6.2. Compressed Archive Logs"
> ('gunzip < /mnt/server/archivedir/%f > %p') did not work for me, because the
> archive_command ('gzip < %p > /var/lib/pgsql/archive/%f') alters the
> filename to %f.gz
On which platform please? Using a pipe with gzip does not alter the
output file name where the data is pushed to.
> I had to change the restore_command to 'gunzip <
> /mnt/server/archivedir/%f.gz > %p'.
Now, I kind of agree that compressing a file and not using a proper
.gz extension for its name can be confusing. So what about the
attached to tweak both archive_command and restore_command in this
section of the docs?
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| doc-archive-gz.patch | text/x-diff | 828 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philipp Gramzow | 2021-02-24 06:24:17 | Re: incoorect restore_command |
| Previous Message | Michael Paquier | 2021-02-24 05:29:31 | Re: pgbench: supports PGDATABASE / warning about -d |