Date: Fri, 9 Feb 2024 10:06:28 +0100 (CET)
From: gparc@free.fr
To: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-docs <pgsql-docs@lists.postgresql.org>
Message-ID: <1787777342.368448490.1707469588843.JavaMail.zimbra@free.fr>
In-Reply-To: <ZcVNlVIEa5BOpmdE@tamriel.snowman.net>
References: 
 <170738227967.3279716.16428042124969376330@wrigleys.postgresql.org>
 <ZcTCTQKLmJBYUwHF@tamriel.snowman.net>
 <705658729.361810855.1707401435362.JavaMail.zimbra@free.fr>
 <ZcVNlVIEa5BOpmdE@tamriel.snowman.net>
Subject: Re: Add a different archive_command example for Linux / Unix
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Thread-Topic: Add a different archive_command example for Linux / Unix
Thread-Index: zc2VQzaBWMOtgPcSDZ5jll2xqtp/4Q==
Archived-At: 
 <https://www.postgresql.org/message-id/1787777342.368448490.1707469588843.JavaMail.zimbra%40free.fr>
Precedence: bulk


Hello Stephen,

For the missing fsync directory, in case of a system crash which I had in m=
ind using this command,
I thought that fsck will fixed the discrepancy.

I support your proposal i.e. archive_command =3D 'backup_tool %p /mnt/serve=
r/archivedir/%f'
as at least people will investigate what choices they have for backup tools=
.

Regards
Gilles


----- Mail original -----
> De: "Stephen Frost" <sfrost@snowman.net>
> =C3=80: "gparc" <gparc@free.fr>
> Cc: "gparc" <gparc@online.fr>, "pgsql-docs" <pgsql-docs@lists.postgresql.=
org>
> Envoy=C3=A9: Jeudi 8 F=C3=A9vrier 2024 22:54:29
> Objet: Re: Add a different archive_command example for Linux / Unix

> Greetings,
>=20
> * gparc@free.fr (gparc@free.fr) wrote:
>> Thanks Stephen for your detailed reply and broad perspective.
>> But I see the cp example command used **as is** most of the time.
>=20
> In those cases- how would changing it to be a dd command be helpful?
> The directory still wouldn't be fsync'd and there's a very good chance
> that the rest of the documentation isn't followed or understood either,
> leading almost certainly to broken backup setups.  This wouldn't be the
> only issue in any case, to be sure.
>=20
> This comes back to my earlier suggestion that perhaps we should just
> change it to something like:
>=20
> archive_command =3D 'backup_tool %p /mnt/server/archivedir/%f'
>=20
> and not talk about specific tools that exist but don't perform in the
> manner we actually expect from an archive command that we're using.  We
> already make it pretty clear to anyone who knows the tools mentioned
> that the 'example' command won't work, if you read everything under that
> section.
>=20
> Alternatively, we could actually document the tools we're aware of that
> do work and which do strive, at least, to try and be good backup tools
> and good archive commands for PG.  That would certainly be a service to
> our users and might result in far fewer misconfigured systems using the
> examples because they thought (despite the explicit note in our
> documentation) that they were recommendations.
>=20
> Thanks,
>=20
> Stephen