pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Philipp Gramzow <phil@philphonic.de>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: incoorect restore_command
Date: Fri, 26 Feb 2021 11:54:18 -0500
Message-ID: <20210226165418.GY20766@tamriel.snowman.net> (raw)
In-Reply-To: <478b5b00-5ab3-a1b5-65f4-19b4409c720b@philphonic.de>
References: <161397938841.15451.13129264141285167267@wrigleys.postgresql.org>
	<YDXo2tIJmkW6mhkm@paquier.xyz>
	<478b5b00-5ab3-a1b5-65f4-19b4409c720b@philphonic.de>

Greetings,

* Philipp Gramzow (phil@philphonic.de) wrote:
> Am 24.02.2021 um 06:49 schrieb Michael Paquier:
> >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.
> We're on RHEL 7. Thanks for pointing out my mistake, someone altered our
> archive_command to use .gz extensions without me noticing it. Please excuse
> the confusion.

Note that the simple commands in the documentation are really just to
give you an example of what an archive command would look like- they
shouldn't be used verbatim since they don't provide any guarantees that
the resulting compressed file has actually been written out to disk
(something that an archive command really should provide the guarantee
of- otherwise a crash will result in WAL files likely going missing and
therefore you'll lose the ability to do PITR).

Thanks,

Stephen

Attachments:

  signature.asc (application/pgp-signature, 818B) download

view thread (9+ messages)

Message-ID: <20210226165418.GY20766@tamriel.snowman.net>
Permalink:  ../20210226165418.GY20766@tamriel.snowman.net/
Also on:    postgresql.org/message-id/20210226165418.GY20766@tamriel.snowman.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: sfrost@snowman.net, phil@philphonic.de, michael@paquier.xyz, pgsql-docs@lists.postgresql.org
  Subject: Re: incoorect restore_command
  In-Reply-To: <20210226165418.GY20766@tamriel.snowman.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox