Using the PG17 support branch, for now we have the following failing regression tests:

• multi-1 schedule: 17/226 tests failing
• multi schedule: 22/185 tests failing
• multi-mx schedule: 3/68 tests failing
• columnar schedule: 2/43 tests failing
• isolation schedule: 2/95 tests failing
• vanilla schedule: 2/222 tests failing
• enterprise schedule: 8/31 tests failing
• arbitrary-configs schedules: 1/29 tests failing
• failure schedule: 1/39 tests failing
• pg16-pg17 upgrade failing
• pg15-pg17 upgrade failing
• installcheck schedule failing, cdc_wal2json test fails because wal2json package is not available yet for pg17

Fixed:

• multi schedule stuck at drop_column_partitioned_table test
• multi-mx schedule stuck at start_stop_metadata_sync test
• columnar schedule stuck at columnar_create test

timeout issue fixed by Check if there are blocks left in columnar_scan_analyze_next_block

• vanilla schedule: 50/222 tests failing, dropped to 4/222 failing

crash fixed by Check whether table AM is default

• multi-mx schedule had 22/68 tests failing, dropped to 3/68 failing

fixed by colliculocale daticulocale renamed to colllocale datlocale, fix some …

• vanilla schedule: 4/222 tests failing, dropped to 2/222 failing

fixed by Add COLLPROVIDER_BUILTIN option