Обсуждение: BUG #19339: odbc_fdw extension, Not able to read data from foreign tables

The following bug has been logged on the website:

Bug reference:      19339
Logged by:          Vijay Reddy
Email address:      vijay.reddy@programming.com
PostgreSQL version: 17.6
Operating system:   Windows 2022
Description:

Dear PostgreSQL team,

I am facing an issue with odbc_fdw. I need your help.

Tasks completed: 1.  Downloaded fdw_win64_17_bin
    2.  Odbc_fdw  extension created.
    3. Created Foreign server  ( Reports_server)
     4. Tested DSN between odbc and sql db ( remote live db) successfully
     5. User mapping done: mapped ‘postgres’ user to  sql_prod_account/*****
     6. Created foreign tables.
     7. Select * from the public.”IpInfo”  failed  with driver error.
     8. Postgres user not speaking to odbc
     9. Tds_fdw files downloaded, right binary not available, not able to
create tds_fdw extension with available binaries.
    10. ODBC Driver 17 for SQL Server is compatible with and DSN tested
successfully and connected via 1433 and user/password to live db
     11.  Re-started postgres service with ‘Local System Account’ and
‘Network Service’ Account.


Issue: Not able to read foreign table data (from Remote SQL DB) due to
error.

Error:  Connecting to driver
SQL State: 58000
PostgreSQL service process can not load the odbc driver or connect to the
DSN defined file.

On Tue, Dec 2, 2025 at 3:29 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
> I am facing an issue with odbc_fdw. I need your help.

[snip]

> Issue: Not able to read foreign table data (from Remote SQL DB) due to
> error.
>
> Error:  Connecting to driver
> SQL State: 58000
> PostgreSQL service process can not load the odbc driver or connect to the
> DSN defined file.

I think that this message was produced by the extension.

The extension is developed externally, not by the Postgres project, so
I recommend sending this to the development team of it.

Best regards,
Etsuro Fujita

On Thu, Dec 11, 2025 at 12:51 AM Vijay Reddy
<vijay.reddy@programming.com> wrote:
> The issue is resolved. We were able to fix the issue internally.

That's good to hear!

Best regards,
Etsuro Fujita