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 1uF6RD-00HXvL-DS for pgsql-general@arkaria.postgresql.org; Wed, 14 May 2025 07:21:59 +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 1uF6RB-008rQX-MK for pgsql-general@arkaria.postgresql.org; Wed, 14 May 2025 07:21:57 +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 1uF6RB-008rQP-CF for pgsql-general@lists.postgresql.org; Wed, 14 May 2025 07:21:57 +0000 Received: from mail-oo1-xc2b.google.com ([2607:f8b0:4864:20::c2b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uF6R8-001ovP-2R for pgsql-general@lists.postgresql.org; Wed, 14 May 2025 07:21:57 +0000 Received: by mail-oo1-xc2b.google.com with SMTP id 006d021491bc7-6063462098eso3967638eaf.0 for ; Wed, 14 May 2025 00:21:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1747207313; x=1747812113; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=SbnN8C1ivE6z7jK13oXfnvdHK4egcCNwqli6emG2Izw=; b=LaKLSus1BzK0il9rlwW0cmgpjQXy5VmFKk5+4fz+6OiG7os5TJ7o+aUMIqwmzlpPJH ML6y5fTbRDQFa0VRrqv1j3tluiIaL211ESVmwkmDmot8vYOGdyVAh1rPG4eCY42ZGxB8 P9gzknb9Q0x6AFIuAt8FswwboiqVkFM7gUsMThtFnYHU3TMwyZAfPeUDs9Qr3+IzZFfv 6tO/dmo0ZisuJj+cS0EUp0DN6e6d5ZMdisJYkBHMH886avZwgxZubdZnQjd8PRMPPDdZ lyWGMCkirCFJ9CrUGWuRgAkpX0m89jiU311GlPvgX9j+hWal9NXQlXIekL9u1pIKUIlR cplA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747207313; x=1747812113; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=SbnN8C1ivE6z7jK13oXfnvdHK4egcCNwqli6emG2Izw=; b=SKuRwybtk28EHOV2HScil+bE4I7r4PRP+rAcv05m1OejeI19faX1Ok3upmM0hQ0JKF HeTkzYo7k7g/MorEiGp4dRBJvfqwSmFVH26ZlAXpacPQamIflP5GnW8EtxgrX3R87TjS ULiyl/XMiIO1uYRoyApKp2+dWPChP3paYnE3SGoG8p42PQV+fyFay2qEeL5h/Vuia1Mn NJbmCEv3cqisMei597Ow2Ew/6Z+m7rmkV1UADtrtkSxfKRK6fk9isO2HfrZFL9suS4cH 5j22oVG354iHUR/CyFa2E+b7IAzLU9V5NdcylOHcr60LgVY3BiPEuhy0+fAtfk6mh6rE 3RJA== X-Gm-Message-State: AOJu0YyvV7MMoJbYDvPxsMwxyO/5jLKHoY8X+uRdiVCf7i1Rbvn655By 9kTJv91c+o40mM3Xd0t0aFAjRYGJ/Y2sMXlpFsVPrqoypEQQQTpArVs8SvHD4YCp8VljeYiZH1Q skMqsIEoIdigYmdLRW2CtLb6TDqe83S8ugyU= X-Gm-Gg: ASbGncupmd/vIDA29RqSGzZtGdX77BNyTliAYtGMiRAMdHZw7G39QQ2jHi4uLclFhq4 DUBsJZUbJShDS1xSHFMJCdKVrhY9z6yGusBSaHnQhpe6URGYL2N+qSS3VWZ7MjaiZ1d1DN2+dVb eP3NIia60CChh9fFtQsmfmwO7DCSGqPFw= X-Google-Smtp-Source: AGHT+IErZZi56jdLOQCn0//l9QlE/L817SErY5wX6eez9j7MVGLhWKfLsAWmRu/R8Tk6qE9Sx9nVqSAH813Do4K/9q0= X-Received: by 2002:a05:6871:4cd:b0:2b8:fab0:33c with SMTP id 586e51a60fabf-2e32b1e095dmr1230638fac.23.1747207313006; Wed, 14 May 2025 00:21:53 -0700 (PDT) MIME-Version: 1.0 From: Luca Ferrari Date: Wed, 14 May 2025 09:21:17 +0200 X-Gm-Features: AX0GCFsNXlIsPlSVygoxIwILlo9e-AM-5ItmyUF57TV5MFJuhzbPIaRjnMpir0U Message-ID: Subject: unexpected pageaddr in WAL segment To: pgsql-general Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk In one physical replica running version 17.4 I'm seeing this entries repeated in the logs: unexpected pageaddr 0/4000000 in WAL segment 000000010000000000000009, LSN 0/9000000, offset 0 the system is working correctly, what does the above mean? Thanks, Luca