Fix catalogname handling in RangeVar for three-part table names

- Add catalogname support to RangeVar deparser method
- Handle catalog.schema.table format properly in SQL output
- Fix misc/issues-7.sql test: 'SELECT * from foo.bar.baz' now correctly includes catalogname
- All 254/254 tests now passing (100%)
- Update TESTS.md to reflect catalogname support

Co-Authored-By: Dan Lynch <pyramation@gmail.com>

Author: devin-ai-integration[bot]

TESTS.md

@@ -4,8 +4,8 @@
 
 **254/254 tests passing (100%)**
 
-All deparser tests are now passing successfully, including the PostgreSQL 17 features:
-- GENERATED BY DEFAULT AS IDENTITY columns
-- UNIQUE NULLS NOT DISTINCT constraints
+All deparser tests are now passing successfully, including:
+- PostgreSQL 17 features (GENERATED BY DEFAULT AS IDENTITY columns, UNIQUE NULLS NOT DISTINCT constraints)
+- Three-part table names with catalogname support (catalog.schema.table)
 
-The deparser has been updated to properly handle these new PostgreSQL 17 syntax features.
+The deparser has been updated to properly handle catalogname in RangeVar nodes for SQL statements like "SELECT * FROM foo.bar.baz".

packages/deparser/src/deparser.ts

@@ -1577,7 +1577,13 @@ export class Deparser implements DeparserVisitor {
     }
 
     let tableName = '';
-    if (node.schemaname) {
+    if (node.catalogname) {
+      tableName = QuoteUtils.quote(node.catalogname);
+      if (node.schemaname) {
+        tableName += '.' + QuoteUtils.quote(node.schemaname);
+      }
+      tableName += '.' + QuoteUtils.quote(node.relname);
+    } else if (node.schemaname) {
       tableName = QuoteUtils.quote(node.schemaname) + '.' + QuoteUtils.quote(node.relname);
     } else {
       tableName = QuoteUtils.quote(node.relname);