Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pDBGw-00037x-K3 for pgsql-general@arkaria.postgresql.org; Wed, 04 Jan 2023 21:26:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pDBFx-00058I-8G for pgsql-general@arkaria.postgresql.org; Wed, 04 Jan 2023 21:25:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pDBFw-00057z-Rh for pgsql-general@lists.postgresql.org; Wed, 04 Jan 2023 21:25:04 +0000 Received: from mail-oi1-x22a.google.com ([2607:f8b0:4864:20::22a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pDBFu-0007Mo-ME for pgsql-general@lists.postgresql.org; Wed, 04 Jan 2023 21:25:04 +0000 Received: by mail-oi1-x22a.google.com with SMTP id h185so8060067oif.5 for ; Wed, 04 Jan 2023 13:25:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-language:thread-index:content-transfer-encoding :mime-version:message-id:date:subject:in-reply-to:references:to:from :from:to:cc:subject:date:message-id:reply-to; bh=RUjfNVeW+3jh1XynnxrCj0+FsyQ2WbhM2h4vkl31nwc=; b=Ce+Tw3mjd2+LZArL4MoWrPY5ZOTyBUstCXRNxc8ZtIsnQgQYYZA1m4xJTwn3xyGeC7 ivzhx6RoNSnbkP2UmTCkVhMg8CTv4cc494X8q3jOmhCnWrfyIoTWnqj0fNbVRzB/TMpT lyzYuIe+YfGn155g8sJlskyxW/1sSHCfjnR3VRh3RIwxxDJhER+JvPLYRit31w7LFUsa czNJbQIT4rxYPxBQoLxBbET6ZBg/6OfuZq+3MwxdVhAyuB1s8Z+AwV5ZtmxhhQp9NUBw ozpik2eXrhKujHZ0Ylxb8ae8JWVSLlPGwC3rkEdgvN5gu2LAfAZLQ+uY5H4hBv/jFAZt +4gw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-language:thread-index:content-transfer-encoding :mime-version:message-id:date:subject:in-reply-to:references:to:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=RUjfNVeW+3jh1XynnxrCj0+FsyQ2WbhM2h4vkl31nwc=; b=SP1WevPkP9Z9BjGGdoZJvfIFQCC8PHPwHv8TQOZi3+HLtlBTQbxRjRjqyxJrsxTou8 grzPfzTCARe2PwHp4Zkw2+3g3XHh5KLoTB0BZP5G6Jy4anmceWO8iYOhf1OYlGxbCIGP /zykxT033qpRNSmfcx/IOkz5e5NQx+Q7R4rL0Mzdd7UePMxF3APlFTYRrrIHUMfJWaWF VDc2DkzJbruXclT6TMFZx58TdBKH/Zx917xu26ySXrQmCoAKlxSEzKWMmOeEBHsNgfe4 7mKjZXpCUxYZgCF/Hw870VmGO2rF65+/S8S9izrKOEVf3qR0iFMW6WLMKlb2x0Wms/zc kLig== X-Gm-Message-State: AFqh2koWi5X1a+Tgip44XEjwi2UUh9wDwMSV7viaHW4o8A4kRUX8EWmM /uo5kYyo4cpEAzBbshQ0qt1dzLb3SDg= X-Google-Smtp-Source: AMrXdXudq8+d8hkcwmOifUtOv81OLUVzKdByTFnEeYlf+mL+eJQM0OPXrWKAUja38292/GxEJskldg== X-Received: by 2002:a05:6808:cc:b0:35e:bd7e:c89c with SMTP id t12-20020a05680800cc00b0035ebd7ec89cmr24015014oic.24.1672867500607; Wed, 04 Jan 2023 13:25:00 -0800 (PST) Received: from DanielF ([190.183.58.215]) by smtp.gmail.com with ESMTPSA id n17-20020a05680803b100b0035ea6f1972esm14644644oie.34.2023.01.04.13.24.59 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Jan 2023 13:25:00 -0800 (PST) From: "Fontana Daniel \(Desartec S.R.L.\)" To: References: In-Reply-To: Subject: Corrupt WAL in replication slot Date: Wed, 4 Jan 2023 18:24:57 -0300 Message-ID: <004b01d92083$0048b5b0$00da2110$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdkfxjtvPeEoxb/qS2umctsNFCaukgAvFrxA Content-Language: es-ar X-Antivirus: Avast (VPS 230104-4, 4/1/2023), Outbound message X-Antivirus-Status: Clean List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk In a replication scheme, one of the satellite databases that replicates against a consolidated database has one of the WAL files corrupted, more precisely the 000000010000000000000000009 file. I try the pg_replication_slot_advance() function to move pg_lsn to skip the= error, but it tells me there is a data inconsistency. You must control the data consistency even though I want to skip them. As an observation, the base checkpoint is much further ahead. Is it possible to regain control of the replication slot? -- Este correo electr=C3=B3nico ha sido analizado en busca de virus por el sof= tware antivirus de Avast. www.avast.com