| From: | Robert Haas <rhaas(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Fix a confusing amcheck corruption message. |
| Date: | 2021-03-16 19:48:14 |
| Message-ID: | E1lMFfq-0006gL-UQ@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Fix a confusing amcheck corruption message.
Don't complain about the last TOAST chunk number being different
from what we expected if there are no TOAST chunks at all.
In such a case, saying that the final chunk number is 0 is not
really accurate, and the fact the value is missing from the
TOAST table is reported separately anyway.
Mark Dilger
Discussion: http://postgr.es/m/AA5506CE-7D2A-42E4-A51D-358635E3722D@enterprisedb.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/4078ce65a0f7197180a9be2c6460ea4bf909bd98
Modified Files
--------------
contrib/amcheck/verify_heapam.c | 8 ++++----
src/bin/pg_amcheck/t/004_verify_heapam.pl | 3 +--
2 files changed, 5 insertions(+), 6 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-03-16 20:03:22 | pgsql: Avoid corner-case memory leak in SSL parameter processing. |
| Previous Message | Stephen Frost | 2021-03-16 18:48:08 | pgsql: Improve logging of auto-vacuum and auto-analyze |