This test was failing because MD5 computations are not supported in
these environments. This switches the test to rely on sha256() instead,
providing the same coverage while avoiding the failure.
Oversight in
f57e214d1cbb. Per buildfarm members gecko, molamola,
shikra and froghopper.
Discussion: https://postgr.es/m/aKJijS2ZRfRZiYb0@paquier.xyz
index 1930eedb8505f6e0d56e2bd6ba2bb8e7d9f17df1..9a2d10600b39fd68da0d3a923151b06e937b91bc 100644 (file)
-- Seed data: one row with big string to force TOAST tuple and trigger the todo=0 code path.
INSERT INTO cluster_toast_value(flag, value)
- VALUES (0, repeat(md5('1'), 120) || repeat('x', 8000));
+ VALUES (0, repeat(encode(sha256('1'), 'hex'), 120) || repeat('x', 8000));
CLUSTER cluster_toast_value;
}