Onur Tirtir 1c51ddae49 Fall-back to seq-scan when accessing columnar metadata if the index doesn't exist ... Fixes #6570. In the past, having columnar tables in the cluster was causing pg upgrades to fail when attempting to access columnar metadata. This is because, pg_dump doesn't see objects that we use for columnar-am related booking as the dependencies of the tables using columnar-am. To fix that; in #5456, we inserted some "normal dependency" edges (from those objects to columnar-am) into pg_depend. This helped us ensuring the existency of a class of metadata objects --such as columnar.storageid_seq-- and helped fixing #5437. However, the normal-dependency edges that we added for indexes on columnar metadata tables --such columnar.stripe_pkey-- didn't help at all because they were indeed causing dependency loops (#5510) and pg_dump was not able to take those dependency edges into the account. For this reason, instead of inserting such dependency edges from indexes to columnar-am, we allow columnar metadata accessors to fall-back to sequential scan during pg upgrades.		2023-01-30 15:58:34 +03:00
..
backend	Fall-back to seq-scan when accessing columnar metadata if the index doesn't exist	2023-01-30 15:58:34 +03:00
bin/pg_send_cancellation	Add jobs to test builds on different distros (#6499)	2022-12-01 19:11:41 +03:00
include	fix multi level recursive plan (#6650)	2023-01-27 21:25:04 +03:00
test	Fall-back to seq-scan when accessing columnar metadata if the index doesn't exist	2023-01-30 15:58:34 +03:00