Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sFYLw-003N8o-JG for pgsql-general@arkaria.postgresql.org; Fri, 07 Jun 2024 12:05:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sFYKv-00BHbq-Rj for pgsql-general@arkaria.postgresql.org; Fri, 07 Jun 2024 12:04:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sFYKv-00BHbi-E0 for pgsql-general@lists.postgresql.org; Fri, 07 Jun 2024 12:04:50 +0000 Received: from mail-oa1-x2a.google.com ([2001:4860:4864:20::2a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sFYKt-000SLF-EI for pgsql-general@postgresql.org; Fri, 07 Jun 2024 12:04:49 +0000 Received: by mail-oa1-x2a.google.com with SMTP id 586e51a60fabf-250e4c4d650so1018834fac.2 for ; Fri, 07 Jun 2024 05:04:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717761885; x=1718366685; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=Vt8rnVTG/OKwsMrxFtYtZIESy5T1yAIEs1eZgWp/7PY=; b=l+mncL1ofZ++1MjKWnjHRhriHHE0TP1vZw2d2/ly+PMqOB6vFEwmqjWZQJhCSYvvTv Dg+iHO8jmA49qWUHDp+PkMmRA3B2LK8N5hVUEnmmDsmZ6jBC2WtR0OOkVnuKzLFEyA6e hjDwmI65sAP32BaAtFbuBddRaLOlmVDLcYcjREvPVZVSYuEnAcICdEm7kOzMGmGFd9ps +ypf3G90rzIz2FirkgtPaKVjmfK6u4Js1enppahwmDy33iniPsDrrE+W6eqauIk29O6+ kQlaqpblpz3i+JQSyw8MjykdwgRZ1SHk+BJHFrKkrjeo463i9SUi24Eb0xU59BhMlJ4N 1kbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717761885; x=1718366685; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Vt8rnVTG/OKwsMrxFtYtZIESy5T1yAIEs1eZgWp/7PY=; b=jJpnosD0r7bP74M4YfMI0P5+jXMUSJ3aL7/IcUpwzuISXJwbfKvWrs85EsEjgyJUpC xGy3Mqn/Lmn/u9+ClmKYfzo6UbMuuBTxKJM7QmFaOM73wqUeieYZcNyj/NgtK5WhvKzY MmA4DGsIMvKZhN3NeHXHlyIL7fDPquyv7NxXLLmM20wCTObUeEhIKxsSL3i7zFBlskuI sf0yiISlUFeZuG/Gyx2DN/FKPXsIYMzh/u29LUI/VEaq/S8XzVGBDptFj/K56kuhtj+3 hNtay9kzooCQ8OYQRkNbzvMBO/TmrfgSnTOjlf3yTQ1mCd0ApyBfgY15LnaAaf0z0JWt fiew== X-Gm-Message-State: AOJu0YzFwVH0OQCvSwL0+z+2dE5bwzD5i5ZaPcPbveKOZF/K+H3EbhMZ pwjObtm3i5V9peu/+c7jhC1/d7wIYmz090vx75eH4DlWhhZdFlxqqqaMXQTRWAg63VKglnKnmXQ KuJvkSLPw8LikQpbFNZCCiX1BvEHwlbH6 X-Google-Smtp-Source: AGHT+IHgq0d28kwDRwG9m1nWKArmB4AHgwdY5b+mREg78RMrD01TZ2GOTzv6wJvFAod3lv+VNmZjrodGswJhBusLQfk= X-Received: by 2002:a05:6870:a194:b0:250:7913:1712 with SMTP id 586e51a60fabf-254645901c8mr2402448fac.35.1717761884576; Fri, 07 Jun 2024 05:04:44 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Fri, 7 Jun 2024 08:04:33 -0400 Message-ID: Subject: Re: PG 14 pg_basebackup accepts --compress=server-zst option To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000f0710a061a4b9a4f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f0710a061a4b9a4f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jun 7, 2024 at 12:32=E2=80=AFAM David G. Johnston < david.g.johnston@gmail.com> wrote: > On Thursday, June 6, 2024, Kashif Zeeshan wrote= : > >> Hi >> >> On Fri, Jun 7, 2024 at 6:54=E2=80=AFAM Ron Johnson >> wrote: >> >>> >>> https://www.postgresql.org/docs/14/app-pgbasebackup.html doesn't >>> mention "--compress=3D[{client|server}-]method". That first appears in= the >>> v15 docs. >>> >>> 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.) >>> >> > Seems a bit suspect, but as your script doesn=E2=80=99t mention tar the o= ption > itself is apparently ignored, I guess silently. > Does this mean that "--compress=3Dserver-zst" is only relevant with --format=3Dtar? > Assuming this isn=E2=80=99t an actual regression in behavior in a patch-r= eleased > older version > My apologies for not mentioning the version: 14.12-1PGDG-rhel8. > I don=E2=80=99t see us adding an error message at this point. > Me neither. It just seemed odd. --000000000000f0710a061a4b9a4f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable --000000000000f0710a061a4b9a4f--