| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Table health |
| Date: | 2023-10-18 14:13:55 |
| Message-ID: | 202310181413.czntq43lzvfu@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 2023-Oct-17, Rajesh Kumar wrote:
> I have been asked to check table health of specific big table.
>
> What are list of things I have to check?
Install extension pg_visibility and run functions pg_check_frozen and
pg_check_visible on the table. I've seen a couple of cases of
**serious** data recoverability issues that aren't discovered until much
later, caused by pages having been improperly marked all-frozen in some
distant past. I assume it's possible to have pages marked as
all-visible as well, which would cause different issues.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Aprender sin pensar es inútil; pensar sin aprender, peligroso" (Confucio)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | richard coleman | 2023-10-18 18:32:07 | What's the state of native Transparent Data Encryption (TDE) in PostgreSQL? |
| Previous Message | Ron | 2023-10-18 14:11:58 | Re: Table health |