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 1qzHRp-00FEIJ-NW for pgsql-admin@arkaria.postgresql.org; Sat, 04 Nov 2023 14:16:25 +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 1qzHRo-0067mt-95 for pgsql-admin@arkaria.postgresql.org; Sat, 04 Nov 2023 14:16:24 +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 1qzHRn-0067ml-UR for pgsql-admin@lists.postgresql.org; Sat, 04 Nov 2023 14:16:23 +0000 Received: from mail-yb1-xb2c.google.com ([2607:f8b0:4864:20::b2c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qzHRl-003vwD-8s for pgsql-admin@lists.postgresql.org; Sat, 04 Nov 2023 14:16:22 +0000 Received: by mail-yb1-xb2c.google.com with SMTP id 3f1490d57ef6-d9ace5370a0so2786076276.0 for ; Sat, 04 Nov 2023 07:16:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699107380; x=1699712180; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=GCJgIRx22qZyCkBYu9uarbhJi+UHpbO1Q/NUVZMpzzw=; b=nCzYgaWkx8WO6wLLWZrbYVyoVA+XbAmNrDS++0TFYsnmqCFaeNhdDsN4vrsH+qAB/7 x8GqZoZUH7PpQ4aAbPIz4EZKDOObWn3asJHG/NwXz5//DAUQABqxOQQh1QuIarxIIria ycsY+YOebXDf3tcdDrr5hQQe9K9b1yoCeg+6MSKvNF8anOXONbRDyJ1w/NBNcWLdMqan vTIiaFQSlrcIescJsO1adxT+AzmprADsBHdzMUdca4TGN2naATOS2qKExSy/AKQ30UKz b/tj/n97P796rRshFQZEvC6kSF1H/WIF+FfxmOba2gjgxewuPx8NCgyH8+MZhnjor5vM g28g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699107380; x=1699712180; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=GCJgIRx22qZyCkBYu9uarbhJi+UHpbO1Q/NUVZMpzzw=; b=FJY3gtRCpsnM/XFuAxbpznDVET83e+YZcFm4AE9pPxWvCs2CHhRG6zYMPNZ2/MChUp mmD9HJYjKE7eWTU2oMHO5ZpssU+wT1MO/Nq34GruPCzDeQZEwsk5dj9DvwEVv/g1mS1P nsWA4qM9LneiMtzuYIbDusJw8pxc5L5pvtAJil+lPf+tLc6YCWc0SPSntAVrUjfJCARr qCexHCRzNZFyEzuRTIOcOXP0XPVdKxnsXIkAdZkOhJiVZW3DktNG/Aq4zZLk2he637cC hp8m0LctIxRWsCjaLrKEqtds4Ssx+tiG6DaYAfwra/V0B9qR9/OoGOQWvoVnyXBzqqrV L+Og== X-Gm-Message-State: AOJu0YyhzpaWqdPWIZtbsKwmtU0vbeQLZo4G679DIMj8Svd7g2Ll63Xr q2BQvEqNQhxzU/WGvzJXmdRFk68IKFM= X-Google-Smtp-Source: AGHT+IE+IHq9k6EDYujuyVdU2PJIN0BNmPVyuoLpv6UIftPnFJl1r2YiLT9zaQK1fCaol3WrJ1bOxQ== X-Received: by 2002:a25:a28b:0:b0:da0:3862:f0a3 with SMTP id c11-20020a25a28b000000b00da03862f0a3mr20527173ybi.5.1699107380126; Sat, 04 Nov 2023 07:16:20 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810::44? ([2600:1700:bd2c:b810::44]) by smtp.googlemail.com with ESMTPSA id 131-20020a250089000000b00d9a577d8434sm1906312yba.53.2023.11.04.07.16.19 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 04 Nov 2023 07:16:19 -0700 (PDT) Message-ID: <8357c11f-388f-436a-bd51-4c4dcbc0ea7a@gmail.com> Date: Sat, 4 Nov 2023 09:16:19 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Recovering standby from primary archived WAL segments Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: <27541699100382@mail.yandex.com.tr> <117cf700fc5db3085f9e294e76f545e3d9ee72f0.camel@cybertec.at> From: Ron In-Reply-To: <117cf700fc5db3085f9e294e76f545e3d9ee72f0.camel@cybertec.at> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/4/23 08:42, Laurenz Albe wrote: > On Sat, 2023-11-04 at 15:46 +0300, Ebubekir Büyüktosun wrote: >> I want to ask how we should configure primary and/or standby servers in case of need >> to recover the standby server from primary archived WAL segments. >> >> If it is possible, how primary and/or standby servers must be configured? > Set "restore_command" on the standby. When using physical replication and a replication slot still exists in pg_replication_slots, won't the WAL files "just" accumulate in pg_wal/ until Pg on the replica is restarted?  (I just tested that, and it seems to work.) -- Born in Arizona, moved to Babylonia.