| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Extending amcheck to check toast size and compression |
| Date: | 2021-05-04 16:43:47 |
| Message-ID: | 20210504164347.GE27406@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
+ /* Oversized toasted attributes should never be stored */
+ if (toast_pointer.va_rawsize > VARLENA_SIZE_LIMIT)
+ report_corruption(ctx,
+ psprintf("toast value %u rawsize %u exceeds limit %u",
+ toast_pointer.va_valueid,
+ toast_pointer.va_rawsize,
+ VARLENA_SIZE_LIMIT));
+
I think the comment sounds wrong since toast is precisely for storage of
"oversized" attributes.
https://www.postgresql.org/docs/current/storage-toast.html
| This section provides an overview of TOAST (The Oversized-Attribute Storage Technique).
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-05-04 16:56:37 | Re: MaxOffsetNumber for Table AMs |
| Previous Message | Robert Haas | 2021-05-04 16:42:04 | Re: .ready and .done files considered harmful |