Hi, Internally at Databricks we've seen rare regression failures in the portals.sql test, where the regression diff looks something like the one attached in data_attachments_ed2b37649a9393b5.diffs.
It seems like this was caused by synchronized seqscans, which caused the foo25ns cursor to start its seqscan not at the start of the table, but instead with an offset into the table. This changed the output, because that relied on the seqscan starting at the first page of the table. To stabilize this test, let's add SET synchronize_seqscans = off, as attached. Kind regards, Matthias van de Meent Databricks (https://www.databricks.com)
data_attachments_ed2b37649a9393b5.diffs
Description: Binary data
v1-0001-Stabilize-syncscan-issue-in-pg_regress-portals.ou.patch
Description: Binary data
