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 1tFU9n-00DGV2-AZ for pgsql-general@arkaria.postgresql.org; Mon, 25 Nov 2024 08:09:19 +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 1tFU9l-00DGpx-S7 for pgsql-general@arkaria.postgresql.org; Mon, 25 Nov 2024 08:09:17 +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 1tFU9l-00DGpp-Dq for pgsql-general@lists.postgresql.org; Mon, 25 Nov 2024 08:09:17 +0000 Received: from mail-lj1-x22e.google.com ([2a00:1450:4864:20::22e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tFU9e-003jmq-SC for pgsql-general@lists.postgresql.org; Mon, 25 Nov 2024 08:09:16 +0000 Received: by mail-lj1-x22e.google.com with SMTP id 38308e7fff4ca-2ffa974b2b0so25140961fa.3 for ; Mon, 25 Nov 2024 00:09:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732522149; x=1733126949; darn=lists.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=3pZBJ1n0k1dezcWX/djk8mmNWf9JWs6bCPGViY/GtDs=; b=d3Y0sNKit7jPEds8jhytufqZwuGlmUuAMYMD6RhimzSD87B0Ggv7pbjL2zHw2eYyYd uMBN3jgdfCbgFLWevEqbK/AcbfFQMG4zpVPW4qXwCv1RzmUuX6YdjlFCsFXJx/LkxmTn zckm2S+7EH5RpZrCIBzhhRZ0SiiZzV1caKPinPzD63ATv0tvQ8KIeZl094ayiAEsrEhP LmlvF16db1+vlozozaN0tD+IB+oi3xF3UgIPmP8trx6beqj+IgGFe2/FsFF3l6S9gkUY /Te6PHQ7PEmTnaG3v7gvrC8HPYbBEpyBPhJtGQNmTYjlw753Xqfq9lhBl6A0zF7xPTkM p2cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732522149; x=1733126949; 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=3pZBJ1n0k1dezcWX/djk8mmNWf9JWs6bCPGViY/GtDs=; b=hULJM/xZZiLIJFDXkTwiIO2xeBPSSzC+zG6I0GGTHBPgo6S6jyaCkJt23veeQehV8U jMkwHuD432wIkfubOAwoCGqyoRxSX4x4O1XSXKI7mInkf3a2tCu421VULn4Ag/dKFS6M 38sKQpKir63UxkBVmlCIcnw7RKyFuHxaUtCf+1euBheASvwXbWHD78xMhxk1QxOCqJSQ zV/BzICq0/7y3lzB47AzYEKWldK5luKTC6xuz65JIdgeE0lINY9s0BUB6Hqg3VHj3BSG i9aTv+h+zlhgjRJ4aJLMXq1sQVos+V01+vS1ajag5UAxs52qZCgYuHLM3RlRtMI32bBU x+jw== X-Gm-Message-State: AOJu0Yxa95uIUvjBE33FMLIhUENz/h1fwLzTGZ7WFuoKRbRpW4DPjgFO 8TDFIeRR72irB6LN/xK35J3sxKXQbjawci9YkIuU4i1eDofLpMa8yol2XKNEiPRnVzoLIp2bMuQ g5XoX46PHsHi75p5TMWyraAztx4U= X-Gm-Gg: ASbGnctlR9Buc9eR5Hmr5FdNutZ/Vm4UZQJiiH+Q5kbw8iOYO/F76BkQ+eYUcswEn+Z yPf0sDNx4lQ0On4jNB1SsvtXzKpgS0oY= X-Google-Smtp-Source: AGHT+IHH3KYj4qXFDIiScILyRLfODlY5PflUBpAguZUAI4Ll+4/ZdK4CIKskBg6QiHKKvntIFaVzFMlkDuZSgdSO8J8= X-Received: by 2002:a2e:a99c:0:b0:2ff:c8a1:c4d1 with SMTP id 38308e7fff4ca-2ffc8a1c6abmr2375751fa.22.1732522148711; Mon, 25 Nov 2024 00:09:08 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: ajit wangkhem Date: Mon, 25 Nov 2024 13:38:56 +0530 Message-ID: Subject: Re: Pg_basebackup failed or completed? To: jayesh thakare Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000003d58780627b83f13" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003d58780627b83f13 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Put wal log in the restore directory and check during start postgresql consumed or not. If consumed then no issue. Instead of risk free create recovery.conf or standby.signal and put restore_command in that above file and see whether consumed or not. If consumed its ok. On Mon, Nov 25, 2024 at 11:10=E2=80=AFAM jayesh thakare wrote: > Hi Team, > > We have got below error while doing basebackup > > > pg_basebackup: could not close file "000000020000022E000000027": No error > > > Can we assume that backup is completed successfully? > > > Regards, > Jayeshthakare > Postgresql DBA > 8828986182 > --0000000000003d58780627b83f13 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Put wal log in the restore directory and check during star= t postgresql consumed=C2=A0or not. If consumed=C2=A0then no issue. Instead = of risk free create recovery.conf or standby.signal and put restore_command= in that above file and see whether consumed or not. If consumed its ok.
On = Mon, Nov 25, 2024 at 11:10=E2=80=AFAM jayesh thakare <thakarejayesh700@gmail.com> wrote:
Hi = Team,

We have got below error = while doing basebackup=C2=A0


pg_basebackup: could not close file "= 000000020000022E000000027": No error

=

Can we assume that backup is = completed successfully?

=
Regards,
Jayeshthakare
Postgresql DBA
8828986182
--0000000000003d58780627b83f13--