Re: incoorect restore_command

2021-02-26 Thread Stephen Frost
Greetings, * Philipp Gramzow (p...@philphonic.de) wrote: > Am 24.02.2021 um 06:49 schrieb Michael Paquier: > >On Mon, Feb 22, 2021 at 07:36:28AM +, PG Doc comments form wrote: > >>I've been trying out saving and restoring compressed archive logs. The > >>restore_command stated in the docs at "

Re: incoorect restore_command

2021-02-25 Thread Michael Paquier
On Thu, Feb 25, 2021 at 06:03:57PM +0900, Fujii Masao wrote: > Regarding the section "Standalone Hot Backups", all the directories and > file seem to be placed under /var/lib/pgsql, so at least for me it looks a bit > strange to change only the path of archive directory. So I don't think that > we

Re: incoorect restore_command

2021-02-25 Thread Fujii Masao
On 2021/02/25 15:54, Michael Paquier wrote: 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,

Re: incoorect restore_command

2021-02-24 Thread Michael Paquier
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/ser

Re: incoorect restore_command

2021-02-24 Thread Fujii Masao
On 2021/02/24 16:52, Michael Paquier wrote: On Wed, Feb 24, 2021 at 07:24:17AM +0100, Philipp Gramzow wrote: I agree, using a proper extension would be more straightforward. I'm sure that's the reason why someone changed our archive_command. Okay, let's do so in the docs then. Others may h

Re: incoorect restore_command

2021-02-23 Thread Michael Paquier
On Wed, Feb 24, 2021 at 07:24:17AM +0100, Philipp Gramzow wrote: > I agree, using a proper extension would be more straightforward. I'm sure > that's the reason why someone changed our archive_command. Okay, let's do so in the docs then. Others may have comments to offer, so I'll first wait a bit

Re: incoorect restore_command

2021-02-23 Thread Philipp Gramzow
Am 24.02.2021 um 06:49 schrieb Michael Paquier: On Mon, Feb 22, 2021 at 07:36:28AM +, 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

Re: incoorect restore_command

2021-02-23 Thread Michael Paquier
On Mon, Feb 22, 2021 at 07:36:28AM +, 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 >

incoorect restore_command

2021-02-22 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/continuous-archiving.html Description: Hi everyone, I've been trying out saving and restoring compressed archive logs. The restore_command stated in the docs at "25.3.6.2. Compressed Arch