ADF using the new Postgresql connector is sometimes getting the error: Message=Could not load type 'NpgsqlTypes.NpgsqlInterval' from assembly 'Npgsql, Version=4.0.9.2. This has been running without error for months.

Question

ADF using the new Postgresql connector is sometimes getting the error: Message=Could not load type 'NpgsqlTypes.NpgsqlInterval' from assembly 'Npgsql, Version=4.0.9.2. This has been running without error for months.

JB 196

We have been using the new ADF Postgresql connector for months without issue but in the last ELT we are getting the error: Message=Could not load type 'NpgsqlTypes.NpgsqlInterval' from assembly 'Npgsql, Version=4.0.9.2.

We are able to successfully extract data from some tables but not others. No ADF changes have been made recently. Is this something that we need to update in ADF, or needs to be updated in the source PostgreSQL databases? I am unsure what the error means and how to fix.

Thank you!

Tony Bravata 5 Reputation points

2025-04-04T15:30:50.8166667+00:00

Having the same issue beginning this morning. Came across this post about it as well. Seems like something changed on Microsoft's end.
JB 196 Reputation points

2025-04-04T15:43:52.19+00:00

Thanks Tony! I saw that link earlier today but I think there had not been any new comments added to it. Though I did see the last comment is showing that they are closing it :(
Hope we can get some answers! Thank you!
JB 196 Reputation points

2025-04-04T16:06:19.2833333+00:00

Like in a comment in the link Tony sent, it looks like our Integration Runtimes were also updated last night. Hopefully they can reopen the ticket?
Venkat Reddy Navari 2,975 Reputation points Microsoft External Staff Moderator

2025-04-04T16:32:18.7533333+00:00
Hi @JB
The error message "Could not load type 'NpgsqlTypes.NpgsqlInterval'." This suggests there may be a compatibility issue between Azure Data Factory (ADF) and the Npgsql library used for PostgreSQL connections. Since this issue is affecting only some tables, it may be related to specific data types, particularly the interval type.

Here’s how you can troubleshoot the issue:

Check the Tables: Please review the schemas of the failing tables. Do they contain interval, time, or timestamp columns? If so, these data types might be causing the issue.

Try a Workaround: You can modify your query to cast the interval columns to text. For example:
SELECT my_interval_column::text FROM my_table;
This adjustment can help keep your ELT process running while we investigate further.

Check for Integration Runtime or Connector Updates: If you are using a self-hosted Integration Runtime, please verify if any updates were applied recently. Additionally, Microsoft may have made backend changes to the ADF PostgreSQL connector that could affect how it handles certain data types.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
JB 196 Reputation points

2025-04-04T16:37:44.02+00:00

Thanks Venkat!

We will check out those troubleshooting steps.
And yes, we did have an update to our self hosted Integration Runtime yesterday and the errors started today.
JB 196 Reputation points

2025-04-04T16:42:31.1933333+00:00

And also, yes for #1, some (havent checked all yet) have timestamp data type columns.
Tony Bravata 5 Reputation points

2025-04-04T16:43:38.3833333+00:00

FWIW, this is affecting all tables I pull from Postgres.

The SHIR did auto update to 5.48.9106.2 in the past 24 hours which corresponds to when the issue started. I noticed that version was a few releases behind the latest one (5.52.9203.1), so I manually updated to the latest and the issue still persists.
JB 196 Reputation points

2025-04-04T21:55:25.72+00:00

MS recommended to downgrade our SHIR to the previous version when things were running OK. Meanwhile they are working on a fix. Will update if downgrading our SHIR to 5.45 temporarily resolves the issue.
JB 196 Reputation points

2025-04-04T21:58:42.8566667+00:00

whoops meant to add the note about downgrading our SHIR to 5.45 temporarily as a comment, not an answer.
BK 0 Reputation points

2025-04-05T22:07:48.1666667+00:00

JB did this solve the issue for you?
Josh Ashwood 96 Reputation points

2025-04-06T02:41:19.7+00:00

Yeah this also affecting us, we also received SSL verification errors. We will downgrade to 5.45.

Do you think you might be able to try to unmark that comment as the answer?

If anyone has updates about a coming fix in a future runtime can you please let us know - thanks!
JB 196 Reputation points

2025-04-06T14:56:59.5766667+00:00

Downgrading to 5.45.899.1 worked for us. I think they are working on a fix so until then this was the workaround.
Leo Ren 5 Reputation points

2025-04-07T08:06:32.2+00:00

Hi,

I also have the same question. it happend after self-hosted Integration Runtime updated to 5.48.9106.2 version.

But it cannot be reproduced stably，it sometimes error and sometimes success when load a same source table。
Nitin S Kavalgi 0 Reputation points

2025-04-08T13:08:17.59+00:00

We are also facing the same issue and the answer provided won't work for on prem postgres db right?

Accepted answer

1 additional answer

Your answer

Tony Bravata 5 Reputation points

2025-04-04T15:30:50.8166667+00:00

Having the same issue beginning this morning. Came across this post about it as well. Seems like something changed on Microsoft's end.
JB 196 Reputation points

2025-04-04T15:43:52.19+00:00

Thanks Tony! I saw that link earlier today but I think there had not been any new comments added to it. Though I did see the last comment is showing that they are closing it :(
Hope we can get some answers! Thank you!
JB 196 Reputation points

2025-04-04T16:06:19.2833333+00:00

Like in a comment in the link Tony sent, it looks like our Integration Runtimes were also updated last night. Hopefully they can reopen the ticket?
Venkat Reddy Navari 2,975 Reputation points Microsoft External Staff Moderator

2025-04-04T16:32:18.7533333+00:00

Hi @JB
The error message "Could not load type 'NpgsqlTypes.NpgsqlInterval'." This suggests there may be a compatibility issue between Azure Data Factory (ADF) and the Npgsql library used for PostgreSQL connections. Since this issue is affecting only some tables, it may be related to specific data types, particularly the interval type.

Here’s how you can troubleshoot the issue:

Check the Tables: Please review the schemas of the failing tables. Do they contain interval, time, or timestamp columns? If so, these data types might be causing the issue.

Try a Workaround: You can modify your query to cast the interval columns to text. For example:
SELECT my_interval_column::text FROM my_table;
This adjustment can help keep your ELT process running while we investigate further.

Check for Integration Runtime or Connector Updates: If you are using a self-hosted Integration Runtime, please verify if any updates were applied recently. Additionally, Microsoft may have made backend changes to the ADF PostgreSQL connector that could affect how it handles certain data types.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
JB 196 Reputation points

2025-04-04T16:37:44.02+00:00

Thanks Venkat!

We will check out those troubleshooting steps.
And yes, we did have an update to our self hosted Integration Runtime yesterday and the errors started today.
JB 196 Reputation points

2025-04-04T16:42:31.1933333+00:00

And also, yes for #1, some (havent checked all yet) have timestamp data type columns.
Tony Bravata 5 Reputation points

2025-04-04T16:43:38.3833333+00:00

FWIW, this is affecting all tables I pull from Postgres.

The SHIR did auto update to 5.48.9106.2 in the past 24 hours which corresponds to when the issue started. I noticed that version was a few releases behind the latest one (5.52.9203.1), so I manually updated to the latest and the issue still persists.
JB 196 Reputation points

2025-04-04T21:55:25.72+00:00

MS recommended to downgrade our SHIR to the previous version when things were running OK. Meanwhile they are working on a fix. Will update if downgrading our SHIR to 5.45 temporarily resolves the issue.
JB 196 Reputation points

2025-04-04T21:58:42.8566667+00:00

whoops meant to add the note about downgrading our SHIR to 5.45 temporarily as a comment, not an answer.
BK 0 Reputation points

2025-04-05T22:07:48.1666667+00:00

JB did this solve the issue for you?
Josh Ashwood 96 Reputation points

2025-04-06T02:41:19.7+00:00

Yeah this also affecting us, we also received SSL verification errors. We will downgrade to 5.45.

Do you think you might be able to try to unmark that comment as the answer?

If anyone has updates about a coming fix in a future runtime can you please let us know - thanks!
JB 196 Reputation points

2025-04-06T14:56:59.5766667+00:00

Downgrading to 5.45.899.1 worked for us. I think they are working on a fix so until then this was the workaround.
Leo Ren 5 Reputation points

2025-04-07T08:06:32.2+00:00

Hi,

I also have the same question. it happend after self-hosted Integration Runtime updated to 5.48.9106.2 version.

But it cannot be reproduced stably，it sometimes error and sometimes success when load a same source table。
Nitin S Kavalgi 0 Reputation points

2025-04-08T13:08:17.59+00:00

We are also facing the same issue and the answer provided won't work for on prem postgres db right?

Answer 1

Pranab Bijoypuri 80

I am also facing the similar issue. Here is my issue.

Problem: I am using the PostgreSQL connector to connect to the on-premises PostgreSQL database. It was working fine and suddenly the connector giving us the problem(Message=Could not load type 'NpgsqlTypes.NpgsqlInterval' from assembly 'Npgsql, Version=4.0.9.2).
Solution: In analysis I found that self-hosted integration run-time(IR) has been updated and problem started after that. I have restarted the self-hosted runtime from the server node. Now it is running perfectly fine.

JB 196 Reputation points

2025-04-09T17:31:11.66+00:00

MSFT gave us the information that the latest SHIR version has been fixed and we should download and use it. We are hoping to do that today. We will update to this version and then restart SHIR and see how it goes. @Pranab Bijoypuri glad you got yours working! Fingers crossed for us too. I will update once we test it. Thanks!

https://download.microsoft.com/download/E/4/7/E4771905-1079-445B-8BF9-8A1A075D8A10/IntegrationRuntime_5.48.9106.2.msi
Nitin S Kavalgi 0 Reputation points

2025-04-10T20:45:16.6933333+00:00

We restarted the SHIR service and it worked
Leo Ren 5 Reputation points

2025-04-11T05:37:14.9366667+00:00

I udapted my IR yesterday and it‘s working great today.

Answer 2

Harrie Kierkels 0

We had the same problem with all PostgreSQL tables in combination with SHIR 5.48.9106.2.
In ADF you can choose between two connectors: "Azure Database for PostgreSQL" and "PostgreSQL".

We've used the last one but we now switched to "Azure Database for PostgreSQL" and that solved our problem!

2025-04-08 11_42_59-screenshot

Share via

ADF using the new Postgresql connector is sometimes getting the error: Message=Could not load type 'NpgsqlTypes.NpgsqlInterval' from assembly 'Npgsql, Version=4.0.9.2. This has been running without error for months.

1 additional answer

Your answer