Chore: Update docs to specify that postgres catalog should use the actual name (#3674)

themisvaltinos · web-flow · commit 163e66b21940 · 2025-01-21T23:34:28.000+02:00
diff --git a/docs/integrations/engines/duckdb.md b/docs/integrations/engines/duckdb.md
@@ -122,6 +122,10 @@ The SQLite database is read-write, while the PostgreSQL database is read-only.
     )
     ```
 
+##### Catalogs for PostgreSQL
+
+In PostgreSQL, the catalog name must match the actual catalog name it is associated with, as shown in the example above, where the database name (`dbname` in the path) is the same as the catalog name.
+
 ##### Connectors without schemas
 
 Some connections, like SQLite, do not support schema names and therefore objects will be attached under the default schema name of `main`.

Original file line number	Diff line number	Diff line change
`@@ -122,6 +122,10 @@ The SQLite database is read-write, while the PostgreSQL database is read-only.`
`122`	`122`	`)`
`123`	`123`	```
`124`	`124`
	`125`	`+##### Catalogs for PostgreSQL`
	`126`	`+`
	`127`	+In PostgreSQL, the catalog name must match the actual catalog name it is associated with, as shown in the example above, where the database name (`dbname` in the path) is the same as the catalog name.
	`128`	`+`
`125`	`129`	`##### Connectors without schemas`
`126`	`130`
`127`	`131`	Some connections, like SQLite, do not support schema names and therefore objects will be attached under the default schema name of `main`.