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 1sRxUW-002TAx-Cm for pgsql-general@arkaria.postgresql.org; Thu, 11 Jul 2024 17:22:00 +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 1sRxUV-00GboU-1b for pgsql-general@arkaria.postgresql.org; Thu, 11 Jul 2024 17:21:59 +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 1sRxUU-00GbmK-Mr for pgsql-general@lists.postgresql.org; Thu, 11 Jul 2024 17:21:58 +0000 Received: from mail-yw1-x112e.google.com ([2607:f8b0:4864:20::112e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sRxUN-001ZH6-3l for pgsql-general@lists.postgresql.org; Thu, 11 Jul 2024 17:21:56 +0000 Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-64d408a5d01so10708457b3.1 for ; Thu, 11 Jul 2024 10:21:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720718510; x=1721323310; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=DI4ZMbAaFvKWpizItY+Y6t6oNCRlidvINlXoRuNKnYc=; b=JP/iZA+dfcAw81aJPh9iFKY4OoscuJ5TJwVvL/uZtg6rmb+GUQqSwJAP0WLJVyE/2Z zmAl8IYRSVQRxyAJ4y0h+vpVNJvaafz6YnIwMypHh7d8LUO7/G1hg/ZE2G6CyRRZbtq5 E7Ri78Mf1RG1o3YtwwDoxIYNWqrWWeDIHDH2RQUokoJfqvRsCWwc16TklVrjlBOW0Dqs Brq7z2l27tYdIvY1NIe3eQy9gyRLCeqwIkpSV67PilQoHYKW6v65SVFb6B/NaBxwT8s3 xcsAcIXWG2n+itcKOCdq4WJyuONnngDyDj888Sya2rLi/w5HMSH7XU8n35LAoWKNP6en RvqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720718510; x=1721323310; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=DI4ZMbAaFvKWpizItY+Y6t6oNCRlidvINlXoRuNKnYc=; b=SgmOkgxPBRGoHxkWlVfTUpGB7uxosbNkwMVE+fJBdrv7bJqnL7yf30/G/yoYMMfuzM ohxS4UKXf6jITwcbPJImb5fXKnVAfhSTzS2iuF6oAEa8ks4kopYN9GRiE/Fdg7vO12Bz 1PZ277cQMfP/R5gViRH852xr07fmrIW2XU2Bcv5nubfQVOD//F41IY9h/sJPLtstEjDm kb4WZi2XSSZI1X3V9VdNrl58KDaygmm041LTTw6DAkQ4M3lVzFqdPRXjnWTB/KXuftZr Dxefx5op2HWGOLGxQZ3Y3zDvhrjLGFLCLHvDy6uYjA0erO7ccJSxQKDrSWezT4NqJafK OFHg== X-Gm-Message-State: AOJu0Yw/+stFo5VPYBaAONLfhLzS9fANZRsm+tHgP/N2aLlqQOsdqrJw Ja3jbuawUn/yxH7hQIz1xffeSCinSdMFms4HMXUtAeHXY0/gHdZ8CDtE++olaGdL4LuG3228I+o 4p8V62apOp1EyS1YhI5nGdBe7d0pRDwxg X-Google-Smtp-Source: AGHT+IFg58rNU9W7EPFlMWCScb7Nv8vNoqtBjy3ResZs/xd6T2sr/sZzUWrQZzUU+/lHcLbv0ZHKHA//IGhGh+gxwKY= X-Received: by 2002:a81:8d4e:0:b0:64b:8b8f:7770 with SMTP id 00721157ae682-659fe401a01mr74765337b3.23.1720718510269; Thu, 11 Jul 2024 10:21:50 -0700 (PDT) MIME-Version: 1.0 From: Gus Spier Date: Thu, 11 Jul 2024 13:21:39 -0400 Message-ID: Subject: page is not marked all-visible but visibility map bit is set in relation "pg_statistic" To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000902dcb061cfbffa2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000902dcb061cfbffa2 Content-Type: text/plain; charset="UTF-8" AWS RDS Postgres Aurora version 14.4 Error log shows: page is not marked all-visible but visibility map bit is set in relation "pg_statistic" To me, that sounds ominous. But, there does not appear to be any great performance hit. The applications are chugging along nicely. The end-users have not yet gathered at my door, waving torches and pitch-forks. What is the correct course of action in this case? Regards, Gus Spier --000000000000902dcb061cfbffa2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
AWS RDS Postgres Aurora version 14.4

Er= ror log shows:=C2=A0page is not marked all-visible but visibility map bit i= s set in relation "pg_statistic"

To me, = that sounds ominous. But, there does not appear to be any great performance= hit. The applications are chugging along nicely. The end-users have not ye= t gathered at my door, waving torches and pitch-forks.

=
What is the correct course of action in this=C2=A0 case?
Regards,

Gus Spier
--000000000000902dcb061cfbffa2--