Naisila Puka b2291374b4 PG16 compatibility - more test output fixes (#7112) ... PG16 compatibility - part 9 Check out part 1 42d956888d part 2 0d503dd5ac part 3 907d72e60d part 4 7c6b4ce103 part 5 6056cb2c29 part 6 b36c431abb part 7 ee3153fe50 part 8 2c50b5f7ff This commit is in the series of PG16 compatibility commits. It makes some changes to our tests in order to be compatible with the following in PG16: - Fix multi_subquery_in_where_reference_clause test somehow PG got rid of the outer join (e.g., explain doesn't show outer joins), hence we can pushdown the subquery. Changing to users_reference_table - Fix unqualified column names for views in PG16 Relevant PG commit: 47bb9db759 47bb9db75996232ea71fc1e1888ffb0e70579b54 - Fix global_cancel test Error wording and detail changed Relevant PG commit: 2631ebab7b 2631ebab7b18bdc079fd86107c47d6104a6b3c6e - Fix local_table_join_test with lateral subquery Possible relevant PG commit: ae89129aa3 ae89129aa3555c263b8c3ccc4c0f1ef7e46201aa I removed the where clause and the limit count error was hit again. With the where clause the query unexpectedly works. - Fix test outputs Relevant PG commits: -- 1349d2790b -- f4c7c410ee For multi_explain and multi_complex_count_distinct there were too many places touched so I just added an alternative test output. For the other tests I modified the problematic parts. More PG16 compatibility commits are coming soon ...		2023-08-15 13:49:25 +03:00
..
backend	PG16 compatibility - varnullingrels additions (#7107)	2023-08-15 13:07:55 +03:00
bin/pg_send_cancellation	Add jobs to test builds on different distros (#6499)	2022-12-01 19:11:41 +03:00
include	PG16 compatibility - Rework PlannedStmt and Query's Permission Info (#7098)	2023-08-09 15:23:00 +03:00
test	PG16 compatibility - more test output fixes (#7112)	2023-08-15 13:49:25 +03:00