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 1uubDu-00DTlr-GY for pgsql-admin@arkaria.postgresql.org; Fri, 05 Sep 2025 18:31:47 +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 1uubDt-009YIo-Lw for pgsql-admin@arkaria.postgresql.org; Fri, 05 Sep 2025 18:31:46 +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 1uubDt-009YIg-8r for pgsql-admin@lists.postgresql.org; Fri, 05 Sep 2025 18:31:45 +0000 Received: from mail-oa1-x2b.google.com ([2001:4860:4864:20::2b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uubDq-000kz9-0h for pgsql-admin@postgresql.org; Fri, 05 Sep 2025 18:31:45 +0000 Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-3197f534179so2104109fac.2 for ; Fri, 05 Sep 2025 11:31:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1757097101; x=1757701901; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZzU36Km6vCzU5SFxZNUmuv9urHj/8ZpJVXkW0mge5e0=; b=KmLEutSTTE1MjjOZblgwvsxAybGM+Fy2XxW2WDqIBG69IqR2/7jdycBVJ1wpX9HlVc s+9OAx2hq5vMRDokiR5kkcEHQk2V90ampI/Hl2dMX/1XAd8cyaL/mf+JYZAuNDT/B4G6 vWyP89emGLBgXYxAw60VM2XT2MwNR+ytEseC+JHjFl30oPjq8AgSptpOo79kuTOSwmsY ggmMGB6iRhbfd8JdX2Og1SXbKIqrZ0HOC6LkDJ9N8Tz4QDKLYXt+vbtPyTWJ8z24eLzI tc1+vBAxPdy1slSi+kf0TvN/+WXdnjvuz7Oxq5hwF7ZarimBxyeymLyzkYUu4YR8tNJb 2yLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1757097101; x=1757701901; h=cc: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=ZzU36Km6vCzU5SFxZNUmuv9urHj/8ZpJVXkW0mge5e0=; b=S+5YGq2RV5S4jh4nY7UFK8UpoS7wwFDl0gfene2tLW8+0Ee4St6ZyBrJUph+5P+U0Z IXf/pzUOlaxq3Zc+nQo+U1Za2+mUvCo4jpHkwpTA0nkOD8o3BxEEIuysA3+INukXUgwD uOspVaU4TM0InvBD6A4LXQNnxGaqECLLU/N4vbn4bMZTbJcYT3CVQ66L9UaZsyL7eIKD lM2j12pcxPXABZiT8W7MZXUvI+E5S+GxJt5UMulwGGQr3qD8H6Pxf8SgX5LxTmUnRCFW pZAi8qBlBy9Kb6RpdmGH4v8AqdJxWUpmS3ZLmtF9n2ckeY7n8+DSJkd67dU2GcyF078s YGLg== X-Gm-Message-State: AOJu0YzNIFneiiXGG4+pG8VGUWImMe5ds3de72x+cCV9HDcozRvcsKJ+ loAMhZUCQN+Q1YnlE09vfH+Fs0Jj672o+s0+TXGea+PkUh010WWFvo/6d4iVSR0OXEJXpr8+YsQ 7z2L/Xed7rFcJlpOwLzsTlmmqDB8X/S4nn1kd X-Gm-Gg: ASbGnctY1zq9rf7upIbTfgF8E28+bdyNZU1LOVpbGVn4OlFiIfr1okDlEOxY/aIzGIr 78R/K7F3HcmU+0QEcrbH8DPjUDuvLyE8JHi+6uLquXXJcMlLh7oQ8Nfo3vE8vmL1qLL7U1F/ZrJ wKdQFCdI11qP8R57mAdPUDwgE8IfKmNURksTieC5e8yNBbcUvcrfl3LkBKzlMAySRnQfKTZI9xk /QJ5zO1 X-Google-Smtp-Source: AGHT+IE0FgLIR9B50eTvWhOd0zAf8PDKHONwALFBDkbGWq283/fCs/eu0M+GQncmDsC8P5F0pLbuThU8rZAlhAD658Y= X-Received: by 2002:a05:6870:c114:b0:300:3df6:921f with SMTP id 586e51a60fabf-3196306a2f7mr9795203fac.8.1757097100824; Fri, 05 Sep 2025 11:31:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Fri, 5 Sep 2025 14:31:29 -0400 X-Gm-Features: Ac12FXybM-GzrEwhukN5_4A2BN3tUGnQ4Pmv5PRz5eWto1obodfcypnsKdcHaTc Message-ID: Subject: Re: pgbackrest with no PITR option configuraton To: "Ghiurea, Isabella" Cc: PGSQL ADMIN Content-Type: multipart/alternative; boundary="00000000000087f48f063e120cc1" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000087f48f063e120cc1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Sep 5, 2025 at 2:26=E2=80=AFPM Ghiurea, Isabella < Isabella.Ghiurea@nrc-cnrc.gc.ca> wrote: > Hi List, > > My requirement is to use pgbackrest for running full PG backups only no > need for PITR. > > How to configure this in archive_command configuration parameter for > pgbackrest conf. > > seems pgbackrest always asks for archive_mode =3Don but I assume in > archive_commnad I can instruct to not use/generate the WAL files. I > trieded archive_command=3D"/bint/rue" but getting error. > > Any other suggestions ? > > "PgBackrest without PITR" sounds like pg_basebackup. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --00000000000087f48f063e120cc1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Sep 5, 2025 at 2:26=E2=80=AFPM Gh= iurea, Isabella <Isab= ella.Ghiurea@nrc-cnrc.gc.ca> wrote:

Hi=C2=A0 List,

My requirement is to use pgbackrest for running full PG backups only=C2= =A0 no need for PITR.

How to configure this in archive_command=C2=A0 configuration parameter f= or pgbackrest conf.

seems pgbackrest always asks for archive_mode =3Don but I assume in arch= ive_commnad I can instruct to not use/generate=C2=A0 the WAL files. I tried= ed archive_command=3D"/bint/rue" but getting error.

Any other suggestions ?



"PgBackrest without PITR" sounds like pg_baseba= ckup.

-- =
Death to &l= t;Redacted>, and butter sauce.
Don't boil me, I'm still aliv= e.
<Redacted> lobster!
--00000000000087f48f063e120cc1--