MIME-Version: 1.0
References: <CANzqJaB=-AUnoXh+V6ayLPbRut7yNt7utL-=0+OK4hdh35-cTQ@mail.gmail.com>
In-Reply-To: <CANzqJaB=-AUnoXh+V6ayLPbRut7yNt7utL-=0+OK4hdh35-cTQ@mail.gmail.com>
From: Kashif Zeeshan <kashi.zeeshan@gmail.com>
Date: Fri, 7 Jun 2024 09:27:07 +0500
Message-ID: <CAAPsdhfQ0GvDuNeMZpe_sccHcM=7dHZq=C6wXbM8zFr_X2FD3g@mail.gmail.com>
Subject: Re: PG 14 pg_basebackup accepts --compress=server-zst option
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000004df16061a4537d3"
Archived-At: <https://www.postgresql.org/message-id/CAAPsdhfQ0GvDuNeMZpe_sccHcM%3D7dHZq%3DC6wXbM8zFr_X2FD3g%40mail.gmail.com>
Precedence: bulk

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

Hi

On Fri, Jun 7, 2024 at 6:54=E2=80=AFAM Ron Johnson <ronljohnsonjr@gmail.com=
> wrote:

>
> https://www.postgresql.org/docs/14/app-pgbasebackup.html doesn't mention
> "--compress=3D[{client|server}-]method".  That first appears in the v15 d=
ocs.
>
> And yet pg_basebackup doesn't complain about an invalid option.
> (Technically, this is a bug; I first noticed it a week after copying a
> script from a PG 15 server to five PG 14 servers, and running it quite a
> few times without fail.)
>
If the support is removed then it should be mentioned in the official
documentation.

Regards
Kashif Zeeshan
Bitnine Global

>
> $ pg_basebackup \
> >             --pgdata=3D$PGDATA \
> >             --dbname=3Dservice=3Dbasebackup \
> >             --verbose --progress \
> >             --checkpoint=3Dfast \
> >             --write-recovery-conf \
> >             --wal-method=3Dstream \
> >             --create-slot --slot=3Dpgstandby1 \
> >             --compress=3Dserver-zst ; echo $?
> pg_basebackup: initiating base backup, waiting for checkpoint to complete
> pg_basebackup: checkpoint completed
> pg_basebackup: write-ahead log start point: 256/BC000028 on timeline 1
> pg_basebackup: starting background WAL receiver
> pg_basebackup: created replication slot "pgstandby1"
> 42567083/42567083 kB (100%), 1/1 tablespace
> pg_basebackup: write-ahead log end point: 256/BC000138
> pg_basebackup: waiting for background process to finish streaming ...
> pg_basebackup: syncing data to disk ...
> pg_basebackup: renaming backup_manifest.tmp to backup_manifest
> pg_basebackup: base backup completed
> 0
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi</div><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Fri, Jun 7, 2024 at 6:54=E2=80=AFAM =
Ron Johnson &lt;<a href=3D"mailto:ronljohnsonjr@gmail.com">ronljohnsonjr@gm=
ail.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-lef=
t:1ex"><div dir=3D"ltr"><div><br></div><div><a href=3D"https://www.postgres=
ql.org/docs/14/app-pgbasebackup.html" target=3D"_blank">https://www.postgre=
sql.org/docs/14/app-pgbasebackup.html</a> doesn&#39;t mention &quot;--compr=
ess=3D[{client|server}-]method&quot;.=C2=A0 That first appears in the v15 d=
ocs.<br></div><div><br></div><div>And yet pg_basebackup doesn&#39;t complai=
n about an invalid option.=C2=A0 (Technically, this is a bug; I first notic=
ed it a week after copying a script from a PG 15 server to five PG 14 serve=
rs, and running it quite a few times without fail.)</div></div></blockquote=
><div>If the support is removed then it should be mentioned=C2=A0in the off=
icial documentation.</div><div><br></div><div>Regards</div><div>Kashif Zees=
han</div><div>Bitnine Global=C2=A0</div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div dir=3D"ltr"><br><div><font face=3D"monospace">$ pg_base=
backup \<br>&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --pgdata=3D$PGDA=
TA \<br>&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --dbname=3Dservice=
=3Dbasebackup \<br>&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --verbose=
 --progress \<br>&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --checkpoin=
t=3Dfast \<br>&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --write-recove=
ry-conf \<br>&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --wal-method=3D=
stream \<br>&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --create-slot --=
slot=3Dpgstandby1 \<br>&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --com=
press=3Dserver-zst ; echo $?<br>pg_basebackup: initiating base backup, wait=
ing for checkpoint to complete<br>pg_basebackup: checkpoint completed<br>pg=
_basebackup: write-ahead log start point: 256/BC000028 on timeline 1<br>pg_=
basebackup: starting background WAL receiver<br>pg_basebackup: created repl=
ication slot &quot;pgstandby1&quot;<br>42567083/42567083 kB (100%), 1/1 tab=
lespace=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 pg_basebackup: write-ahead lo=
g end point: 256/BC000138<br>pg_basebackup: waiting for background process =
to finish streaming ...<br>pg_basebackup: syncing data to disk ...<br>pg_ba=
sebackup: renaming backup_manifest.tmp to backup_manifest<br>pg_basebackup:=
 base backup completed<br>0</font><br></div><div><br></div></div>
</blockquote></div></div>

--00000000000004df16061a4537d3--