The following bug has been logged online:

Bug reference: 1423
Logged by: Farid Zidan
Email address: cpp256 (AT) netscape (DOT) net
PostgreSQL version: 8.0
Operating system: Windows 2000
Description: ODBC SQLTables SQL_ALL_CATALOGS and SQL_ALL_SCHEMAS
options don't work
Details:

You get an incorrect resultset.

ODBC documentation for SQLTables:

If CatalogName is SQL_ALL_CATALOGS and SchemaName and TableName are empty
strings, the result set contains a list of valid catalogs for the data
source. (All columns except the TABLE_CAT column contain NULLs.)

If SchemaName is SQL_ALL_SCHEMAS and CatalogName and TableName are empty
strings, the result set contains a list of valid schemas for the data
source. (All columns except the TABLE_SCHEM column contain NULLs.)

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match