public inbox for [email protected]
help / color / mirror / Atom feedpage is not marked all-visible but visibility map bit is set in relation "pg_statistic"
2+ messages / 2 participants
[nested] [flat]
* page is not marked all-visible but visibility map bit is set in relation "pg_statistic"
@ 2024-07-11 17:21 Gus Spier <[email protected]>
2024-07-11 20:38 ` Re: page is not marked all-visible but visibility map bit is set in relation "pg_statistic" Tomas Vondra <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Gus Spier @ 2024-07-11 17:21 UTC (permalink / raw)
To: pgsql-general <[email protected]>
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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: page is not marked all-visible but visibility map bit is set in relation "pg_statistic"
2024-07-11 17:21 page is not marked all-visible but visibility map bit is set in relation "pg_statistic" Gus Spier <[email protected]>
@ 2024-07-11 20:38 ` Tomas Vondra <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Tomas Vondra @ 2024-07-11 20:38 UTC (permalink / raw)
To: Gus Spier <[email protected]>; pgsql-general <[email protected]>
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.gma...
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-07-11 20:38 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-07-11 17:21 page is not marked all-visible but visibility map bit is set in relation "pg_statistic" Gus Spier <[email protected]>
2024-07-11 20:38 ` Tomas Vondra <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox