database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Fix a confusing amcheck corruption message.

Browse Source 
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
This commit is contained in:
Robert Haas
2021-03-16 15:42:20 -04:00
parent c6fc50cb40
commit 4078ce65a0
2 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
src/bin/pg_amcheck/t/004_verify_heapam.pl
View File

@ -296,7 +296,7 @@ close($file)
$node->start;
# Ok, Xids and page layout look ok. We can run corruption tests.
plan tests => 20;
plan tests => 19;
# Check that pg_amcheck runs against the uncorrupted table without error.
$node->command_ok(['pg_amcheck', '-p', $port, 'postgres'],
@ -489,7 +489,6 @@ for (my $tupidx = 0; $tupidx < ROWCOUNT; $tupidx++)
$header = header(0, $offnum, 2);
push @expected,
qr/${header}final toast chunk number 0 differs from expected value \d+/,
qr/${header}toasted value for attribute 2 missing from toast table/;
}
elsif ($offnum == 14)