MIME-Version: 1.0
References: <CAGbX52Fg2jxqGVZzeQ_QcHSZ8fgDjnVZUJy5NUb5-PAf8fvxkw@mail.gmail.com>
 <52afa4c9-7393-4265-88bb-6393f1b0fb03@aklaver.com> <CAGbX52EyjjOQJUjA0m4+0azs_yH1by63p6hhJg7Y66=VCCqzpA@mail.gmail.com>
 <45e8c44b-2506-41b5-b999-5fdc42472644@aklaver.com> <CAGbX52ENsSHKoTyu5+XfN1o1bZ2w2CJaE1oQnxcm=fj2SyoZXg@mail.gmail.com>
 <8c61a882-f2a7-4661-bb29-aa4b33450c9e@aklaver.com>
In-Reply-To: <8c61a882-f2a7-4661-bb29-aa4b33450c9e@aklaver.com>
From: Koen De Groote <kdg.dev@gmail.com>
Date: Mon, 21 Oct 2024 22:49:44 +0200
Message-ID: <CAGbX52Ho_kP8W3GpcDH98i30wd+TSo44RaGbry8aYfxU0QjOtw@mail.gmail.com>
Subject: Re: Basebackup fails without useful error message
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: PostgreSQL General <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000094ff07062502cbaa"
Archived-At: <https://www.postgresql.org/message-id/CAGbX52Ho_kP8W3GpcDH98i30wd%2BTSo44RaGbry8aYfxU0QjOtw%40mail.gmail.com>
Precedence: bulk

--00000000000094ff07062502cbaa
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

See, I'm reading that, and my conclusion is "Ah great, it will try again,
everything will be fine."

There's a link between the archive_command, pg_basebackup and
wal_sender_timeout, but that link isn't clear from just reading all these
documentation pages when learning about their concepts separately.

It's just too much information to read and then "just know" in your head
that these must be the relations. Especially if you have dozens of other
things to do.

That's my 2 cents.

Regards,
Koen De Groote


On Sun, Oct 20, 2024 at 11:12=E2=80=AFPM Adrian Klaver <adrian.klaver@aklav=
er.com>
wrote:

> On 10/20/24 14:03, Koen De Groote wrote:
>
> > So I'm assuming the process of writing WAL files, if there is an
> > archive_command set, is only considered to be finished after the archiv=
e
> > is written, not just when the WAL file is written in pg_wal.
>
>
> https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-=
ARCHIVING-WAL
>
> "It is important that the archive command return zero exit status if and
> only if it succeeds. Upon getting a zero result, PostgreSQL will assume
> that the file has been successfully archived, and will remove or recycle
> it. However, a nonzero status tells PostgreSQL that the file was not
> archived; it will try again periodically until it succeeds."
>
>
> > Regards,
> > Koen De Groote
> >
> >
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>
>

--00000000000094ff07062502cbaa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>See, I&#39;m reading that, and my conclusion is &quot=
;Ah great, it will try again, everything will be fine.&quot;</div><div><br>=
</div><div></div><div></div><div>There&#39;s a link between the archive_com=
mand, pg_basebackup and=20
wal_sender_timeout, but that link isn&#39;t clear from just reading all the=
se documentation pages when learning about their concepts separately.</div>=
<div><br></div><div>It&#39;s just too much information to read and then &qu=
ot;just know&quot; in your head that these must be the relations. Especiall=
y if you have dozens of other things to do.</div><div><br></div><div>That&#=
39;s my 2 cents.<br></div><div><br></div><div>Regards,</div><div>Koen De Gr=
oote<br></div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Sun, Oct 20, 2024 at 11:12=E2=80=AFPM Adri=
an Klaver &lt;<a href=3D"mailto:adrian.klaver@aklaver.com">adrian.klaver@ak=
laver.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">On 10/20/24 14:03, Koen De Groote wrote:<br>
<br>
&gt; So I&#39;m assuming the process of writing WAL files, if there is an <=
br>
&gt; archive_command set, is only considered to be finished after the archi=
ve <br>
&gt; is written, not just when the WAL file is written in pg_wal.<br>
<br>
<a href=3D"https://www.postgresql.org/docs/current/continuous-archiving.htm=
l#BACKUP-ARCHIVING-WAL" rel=3D"noreferrer" target=3D"_blank">https://www.po=
stgresql.org/docs/current/continuous-archiving.html#BACKUP-ARCHIVING-WAL</a=
><br>
<br>
&quot;It is important that the archive command return zero exit status if a=
nd <br>
only if it succeeds. Upon getting a zero result, PostgreSQL will assume <br=
>
that the file has been successfully archived, and will remove or recycle <b=
r>
it. However, a nonzero status tells PostgreSQL that the file was not <br>
archived; it will try again periodically until it succeeds.&quot;<br>
<br>
<br>
&gt; Regards,<br>
&gt; Koen De Groote<br>
&gt; <br>
&gt; <br>
<br>
-- <br>
Adrian Klaver<br>
<a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank">adrian.klave=
r@aklaver.com</a><br>
<br>
</blockquote></div>

--00000000000094ff07062502cbaa--