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 1sjHft-00H0Oy-UT for pgsql-general@arkaria.postgresql.org; Wed, 28 Aug 2024 12:21:21 +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 1sjHfq-004GH2-Sd for pgsql-general@arkaria.postgresql.org; Wed, 28 Aug 2024 12:21:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjHfq-004GGr-He for pgsql-general@lists.postgresql.org; Wed, 28 Aug 2024 12:21:19 +0000 Received: from mail-lj1-x22d.google.com ([2a00:1450:4864:20::22d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sjHfo-001qFe-Cp for pgsql-general@postgresql.org; Wed, 28 Aug 2024 12:21:17 +0000 Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2f3f25a1713so77822001fa.2 for ; Wed, 28 Aug 2024 05:21:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724847674; x=1725452474; 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=bJWqNTUUZCZ0rwq6RcluxXsixrgDgXzq34zxNAg45cE=; b=Yu2fDLS6YNcv1o3Mzei+5X+LdIQ8wUKYwfiRgjdlJAsrW2TWqDjtpHyIugG8bOCPEp XnYCSJtIOmJmj8EXLxmY+Mr3VkdF2Aruxc2Y4+F6spplEpHVgp6hLuwn7m2c/DgU9TJd tx5U2ZhwRrh1ZYcImVpNRRpYDwA2Sbjrxl6RRt73NvSYH3v9sUVAXFuaPL7Bnpc4zZLQ 0pAk4bNo7HQkgJnu8GiuAtwLEf8cY4JBI/dtE7gGT89lwp1fFodhuZq72Ski12oZSnMw M5+rmABIeGnbMR7LtStEME9SqRqaBWT8hQQw9Q5ZvcL3PyPZGzfUKBxo1pRCo1seM7l1 FiRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724847674; x=1725452474; 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=bJWqNTUUZCZ0rwq6RcluxXsixrgDgXzq34zxNAg45cE=; b=kpaR6AMX/CkDYP2QMUYfNX76e4ZgPL0v7PkizPw4qiqdnHUJknXygwkjez4EFYtpKQ 6zwvCSGPvZrnI7gu5VmM2HcVRjZaTfrAq3Baqe2t2bp5N2EU2E4VEnO9kSzMOt7g8Aig ITpCRKZc4niLoijwyQO7JMlKRpN5fy/Z8NqUioQLsFt6jRT7ZoxnU47EQ2KG7kMrYfBc PaZfC+ic+WmA+35/WxpT8PW9E8bze4rHwHJwJF7yyW/EjziCeDcPDJYWIbKvhD+HkLs9 r+vld50X3rNYFsv4f0o2L10WZ22JshToLflL6xMi/XyKRYsV/px+T80kG5sF8HH5qlcH By2g== X-Gm-Message-State: AOJu0YxrzUdKOsih5AsUfjIERtjW6mxMEz5tZPZgnAj/QJfbvfY4C/Ko cWGDASHPt/A6xGTJ/IdyIFMDXDurpFqYKJBmuUQ4j/Pk1M6u9y8Jkk2Lvs7R8Ov/ynIjn2hV27u ra7PBF5crRNfnQCBBHvWlu9ABBr4= X-Google-Smtp-Source: AGHT+IEeFHYn4lnUFID7IIuCudrSaWvzYhK7zTaa4jkoKqqVPEVi2EixD+mJj4jWEZ6TzfLDVimHn7JEDH1mzD82WuA= X-Received: by 2002:a2e:d09:0:b0:2f3:cd4e:b929 with SMTP id 38308e7fff4ca-2f4f4927f77mr99424921fa.34.1724847673078; Wed, 28 Aug 2024 05:21:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Greg Sabino Mullane Date: Wed, 28 Aug 2024 08:20:34 -0400 Message-ID: Subject: Re: Pgbackrest specifying the default DB necessary/correct way ? To: KK CHN Cc: pgsql-general Content-Type: multipart/alternative; boundary="000000000000d87c630620bd647c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d87c630620bd647c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Aug 28, 2024 at 1:39=E2=80=AFAM KK CHN wrote: > In this DB server I have other databases than the default "edb" > database. Specifying the above line as pg1-database=3Dedb // I a= m > not sure this line is necessary or not ? > The pgbackrest process needs to connect to the database, which means it needs a user and database. You need this variable if you do not have the default database, "postgres". If you have a database named postgres, you can leave this out. Otherwise, yes, it is necessary. pg1-database=3Dedb // specifying like this, will it block other databases > on this server to get backed up ? IF yes how can I overcome this ? > pgBackRest works on a cluster level, so *all* the databases are backed up. Indeed, it is not possible to only backup some of the databases. It's the whole cluster. ( I am just learning and exploring PgbackRest) found online some > reference configurations so using like this ) Probably best to stick to the official docs; this section in particular is worth a read: https://pgbackrest.org/user-guide-rhel.html Cheers, Greg --000000000000d87c630620bd647c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Aug 28, 2024 at 1:39=E2=80=AFAM K= K CHN <kkchn.in@gmail.com> = wrote:
In this DB server=C2=A0 =C2=A0 I ha= ve other databases=C2=A0 than the default=C2=A0 "edb" database.= =C2=A0 =C2=A0 =C2=A0Specifying the above line as=C2=A0 =C2=A0 pg1-database= =3Dedb=C2=A0 =C2=A0// I am not sure this line is necessary=C2=A0 or not ?

The pgbackrest process needs= to connect to the database, which means it needs a user and database. You = need this variable if you do not have the default database, "postgres&= quot;. If you have a database named postgres, you can leave this out. Other= wise, yes, it is necessary.

=C2=A0pg1-database=3Dedb // sp= ecifying like this, will it block other databases=C2=A0 on this server to g= et backed up ?=C2=A0 =C2=A0IF yes how can I overcome this ?

pgBackRest works on a cluster level, so *all* = the databases are backed up. Indeed, it is not possible to only backup some= of the databases. It's the whole cluster.

=C2=A0( I am just learning and ex= ploring PgbackRest)=C2=A0 found online some reference configurations so usi= ng like this )

Probably best to stick to th= e official docs; this section in particular is worth a read:

=

Cheers= ,
Greg


--000000000000d87c630620bd647c--