This is a meta-issue that describes remaining name resolution problems discovered around the 2.0 release.

Issues due to invalid/missing default db

These issues can be solved by either introducing a pseudo-descriptor for the current database when no valid current db is set, or ensuring the current db exists when a session is opened.

• sql: confusing error when creating table with no active db sql: confusing error when creating table with no active db #24056
• sql: errors in client due to use of pg_catalog with non-existent db as current sql: errors in client due to use of pg_catalog with non-existent db as current #23893
• sql: make pg_catalog error out cleanly when no cur db set sql: make pg_catalog error out cleanly when no cur db set #23958
• (only indirectly) sql: current_schema should skip over invalid schemas sql: current_schema should skip over invalid schemas #24472

Outright pg compat bugs

• sql: current_schema should skip over invalid schemas sql: current_schema should skip over invalid schemas #24472
• Support pg_catalog.regclass when casting sql: support pg_catalog.regclass when casting #18856

Unfortunate bugs due to the special CRDB 1.x compatibility "feature"

• v2.0-beta.20180319: Regression in star queries v2.0-beta.20180319: Regression in star queries #24169
• (only indirectly) sql: not-searched index name found already qualified sql: not-searched index name found already qualified #24475

Other bugs due to CockroachDB idiosyncrasies

• sql: not-searched index name found already qualified sql: not-searched index name found already qualified #24475

UX improvements

• sql: Error messages should be improved in case of no matching data source sql: Error messages should be improved in case of no matching data source #22966