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 1sS0ZG-0035Pf-4n for pgsql-general@arkaria.postgresql.org; Thu, 11 Jul 2024 20:39:06 +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 1sS0ZE-000Wu8-SU for pgsql-general@arkaria.postgresql.org; Thu, 11 Jul 2024 20:39:04 +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 1sS0ZE-000Wu0-Fg for pgsql-general@lists.postgresql.org; Thu, 11 Jul 2024 20:39:04 +0000 Received: from mail-ed1-x535.google.com ([2a00:1450:4864:20::535]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sS0ZA-001cFR-Cv for pgsql-general@lists.postgresql.org; Thu, 11 Jul 2024 20:39:03 +0000 Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-58c2e5e8649so3533603a12.1 for ; Thu, 11 Jul 2024 13:38:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1720730339; x=1721335139; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=9LcGtDhW2Dd/ADE/AjxtmsA1xmVsjZujvojP72sr+aQ=; b=bHtWgMQ/JteyoqMtTuxvrlJodVTqTHJBfbOwSFUjpvPx3EK4imdkMV3qPYMkwy4oML smvIZnUn6sUHviZlD2Dszo3DjKTLAthEoMCbO6xdO0BxAAfv+E+h2dRWJz3yN5H6UJpy jmLZEP4UO3xnVG4xnly1AwMbdADX/OwMXeSniMJhIwmdEoSFRIy9gieNz2OtfS9nKLNP 73/XXbL4SZ1XycFO13a9Z3U6fZDvFI1swTAhyM4D0iqik6a/YuYP87JUk7vPlG7Fkqgx MKZWeRw9PLYpejn93QojQwFpPiAyS4o4QQCJS1L5lWffj9iWhxJHlHw2ZCLRiCbg8KuP ng3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720730339; x=1721335139; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=9LcGtDhW2Dd/ADE/AjxtmsA1xmVsjZujvojP72sr+aQ=; b=glcbNYgQrWtLtIXJdH7g3g+exoXQESDF5lGRiTCEcIMaYPBcnKLgWmng7cTDpKvqsU KeyasXOiMaKcIMIG0SnP/IkOwqmLZB6/J0pNPYum+WkSw56bUJfNWniTxSNyqmgRIqe+ kCqe60zl077ypOi3zZ+gzqj/Xod0SVHKFmJ/blcaT36GfEMX9oQZxwX/ZECtR1LC7GAp 7pUz9IcC9Ct1iARr9YzfqK1YAjCbTtMgIPdvxXo4BTa/wMk9bBW9mLOvQ7Q9EpBicUQM WXva6VYNqXWmBVsj+LhYbv0xQeH8i4I1U1z285CUsHLjWug8hs/YK6PNe8cEQbnMGowW 8sdQ== X-Forwarded-Encrypted: i=1; AJvYcCU8AGK9Sq9d9hv2NCXEiEGEjrP4osEqZPCzxkqFJQq2FowYjahrZHA6s2GLHxFyqVXqosUY1rTfwugU97wtmb3kkOfgCY64XIDyi6mRMCMUqEUx X-Gm-Message-State: AOJu0Yxb00cfnku83IuAS/on1/EbqNEqxBNgs72SSv9O+cYBdSXkUYtx 0wVoYjWyYQKhc2YgENYrGKkHVBm5hCFZ3mKU0nkzYNV2A6Hl9kSB+UJ11xbJEg== X-Google-Smtp-Source: AGHT+IFTa/63HvSU/wDLa1/53FG3/0ZoXX8hJvZwwI9gHura0cHMg0nR8HMbHBa2aN3tGzSmwQoaKw== X-Received: by 2002:a50:8e53:0:b0:58a:f14f:4d6d with SMTP id 4fb4d7f45d1cf-599604d633cmr574842a12.19.1720730338599; Thu, 11 Jul 2024 13:38:58 -0700 (PDT) Received: from [10.137.0.18] (ip-86-49-229-30.bb.vodafone.cz. [86.49.229.30]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-594bda308efsm3772597a12.81.2024.07.11.13.38.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 11 Jul 2024 13:38:58 -0700 (PDT) Message-ID: Date: Thu, 11 Jul 2024 22:38:56 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: page is not marked all-visible but visibility map bit is set in relation "pg_statistic" To: Gus Spier , pgsql-general References: Content-Language: en-US From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 7/11/24 19:21, Gus Spier wrote: > AWS RDS Postgres Aurora version 14.4 > I believe RDS and Aurora are two separate products, so I'm a bit confused by this ... > 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? > I'd say you need to report this to AWS support - we have no idea what changes they made in Aurora, and AFAIK they made a lot of changes in this area. That is not to say we don't have any bugs in this area - see for example the discussion in [1], but we are not in position to investigate issues on a proprietary product. regards [1] https://www.postgresql.org/message-id/CAH2-WznuNGSzF8v6OsgjaC5aYsb3cZ6HW6MLm30X0d65cmSH6A%40mail.gmail.com -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company