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 1t2dE4-005j32-Rt for pgsql-general@arkaria.postgresql.org; Sun, 20 Oct 2024 21:12:37 +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 1t2dE2-001iIs-WF for pgsql-general@arkaria.postgresql.org; Sun, 20 Oct 2024 21:12:35 +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 1t2dE1-001iIj-V8 for pgsql-general@lists.postgresql.org; Sun, 20 Oct 2024 21:12:34 +0000 Received: from fout-a1-smtp.messagingengine.com ([103.168.172.144]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t2dDz-001tlH-9S for pgsql-general@lists.postgresql.org; Sun, 20 Oct 2024 21:12:32 +0000 Received: from phl-compute-12.internal (phl-compute-12.phl.internal [10.202.2.52]) by mailfout.phl.internal (Postfix) with ESMTP id EDEAB138018D; Sun, 20 Oct 2024 17:12:29 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-12.internal (MEProxy); Sun, 20 Oct 2024 17:12:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1729458749; x=1729545149; bh=SG8Ux8erN3aB2XHp7bnpnRVhRYWZbiKH1hDOKMcOqV0=; b= gcDwfie0KE6B11fJxgNRNZY4J+eYU/4mRnXmIRtkaAadoTK/X3Y8g30BPmXTdxvm YfIytPn+1GyZB00s3EMNvgFZ7X1zRHxPA4Qr3D6n/wAZY8b+elX8rd+jFrhb5zZd UaRJcaZ0I58jLJ6XTaAFXGCfD/nGwos7Iyxo1IXfUGRE2TZ+EJkikwysYM3y5hdI zBgw1aHzhTLk6zchYP7KeZaRSRdXgzqgSjikSXsm04OxutDSH0teR2PAo7KXj4DP FJEpYGB0pMuDRcNe/r6AVQ3ukSu7FLfm/49Cd2Fsr3J2kjIeSChwNew7dL5Rsp8O 9vWf2wVNxlnIR05z2m5kSg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1729458749; x= 1729545149; bh=SG8Ux8erN3aB2XHp7bnpnRVhRYWZbiKH1hDOKMcOqV0=; b=d AjVQXlhws7kh/3L6OHi5hXdllkzbR6/FhJh1T37m84oZsCRlDBrTLLrf2NhqEtq5 NeBGTuI8usUDyfw+Q7yIlOCqMmbJ5sBM3laHb2YTVIhxPUSi3zdlrwKv571Ki++z GSpY2bTfKy1BBIEZt6g5b97f8Zc4VRyozX0uzAjy2B/akqFEFI2dsKU/RMuFN5yP cWE2zMUToXqtkuqe/x2Qlj/LpKeYw/00r2e8EyTY5hTX5Vv+52BfeIuhENKCy5Mz 8MustHRUqAb0ywZu8L9KPFiKev82G1oSk0e/XcIse9h5lkyJTuu/e6oORLzWnT/j W8gEGfYKL/gUD+yq3xucg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrvdehjedgudehjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfevfhfhjggtgfesthejredttddv jeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvg hrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeeuudefjeejgffgtddt geehgfekueevkeekieettedtkeffheeivdethfevffegueenucffohhmrghinhepphhosh htghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnh gspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepkhgughdr uggvvhesghhmrghilhdrtghomhdprhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlse hlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 20 Oct 2024 17:12:29 -0400 (EDT) Message-ID: <8c61a882-f2a7-4661-bb29-aa4b33450c9e@aklaver.com> Date: Sun, 20 Oct 2024 14:12:28 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Basebackup fails without useful error message To: Koen De Groote Cc: PostgreSQL General References: <52afa4c9-7393-4265-88bb-6393f1b0fb03@aklaver.com> <45e8c44b-2506-41b5-b999-5fdc42472644@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10/20/24 14:03, Koen De Groote wrote: > So I'm assuming the process of writing WAL files, if there is an > archive_command set, is only considered to be finished after the archive > is written, not just when the WAL file is written in pg_wal. https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-ARCHIVING-WAL "It is important that the archive command return zero exit status if and only if it succeeds. Upon getting a zero result, PostgreSQL will assume that the file has been successfully archived, and will remove or recycle it. However, a nonzero status tells PostgreSQL that the file was not archived; it will try again periodically until it succeeds." > Regards, > Koen De Groote > > -- Adrian Klaver adrian.klaver@aklaver.com