mirror of
https://github.com/postgres/postgres.git
synced 2025-04-22 23:02:54 +03:00
In 002_blocks.pl, try to prevent a HOT update.
Make the new tuple larger than the old one so that it, hopefully, won't manage to squeeze into leftover freespace on the same page. The test is trying to verify that the UPDATE touches 2 pages, but if a HOT update happens, then it doesn't. Per buildfarm.
This commit is contained in:
parent
f0106b6d2d
commit
b6ee30ec08
@ -56,7 +56,8 @@ note_wal_summary_dir("after insert", $node1);
|
||||
|
||||
# Update a row in the first block of the table and trigger a checkpoint.
|
||||
$node1->safe_psql('postgres', <<EOM);
|
||||
UPDATE mytable SET b = 'abcdefghijklmnopqrstuvwxyz' WHERE a = 2;
|
||||
UPDATE mytable SET b = 'abcdefghijklmnopqrstuvwxyz' || b || '01234567890'
|
||||
WHERE a = 2;
|
||||
CHECKPOINT;
|
||||
EOM
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user