Binary column error from postgresql

[And]

Hi!

I Have an interesting problem with connecting to table from postreSQL.

This table include a column with binary type, this column is not neccery for me, I need all others.

When I'm trying to connect to data base or to this table I receive an error in Power BI:

"This native database query returned a type which isn't currently supported. Column: 'kind'."

I also receive this error, when I'm trying to make a data flow. Power BI doesn't want to read anything else after this column, so I can't take off this column.

But, what is interesting, on another machine, Power BI read all columns, all tables, make refresh and only mark "error" in rows of this column. And it makes possible to work with this data base.
Windows on this machines are x64 both, and version of power bi and npgsql are the same.

It will be great if someone can make an advice for me, how can I solve this?

[v-piga-msft · Accepted solution]

Hi @And ,

For your scenario, I have two more questions.

1. Do you have the same client for postgresql in the two machine?

2. Do you have the same operating system Windows Server or Windows 10?

If you both of the above are same, please have a test follow the step below.

You could open the pbix which could load data successfull in the another machine which cannot load the data successfully. If you could run the pbix successfully, I think that the previous issue may be caused by the temporary error or the policy which setting such as the firewall.

Best  Regards,

Cherry

[v-piga-msft · Accepted solution]

Hi @And ,

For your scenario, I have two more questions.

1. Do you have the same client for postgresql in the two machine?

2. Do you have the same operating system Windows Server or Windows 10?

If you both of the above are same, please have a test follow the step below.

You could open the pbix which could load data successfull in the another machine which cannot load the data successfully. If you could run the pbix successfully, I think that the previous issue may be caused by the temporary error or the policy which setting such as the firewall.

Best  Regards,

Cherry

[And]

@v-piga-msft  Thank you very much!!!

The problem was in Windows 10 firewall. After turnning off some settings all become Ok.

[And · Accepted solution]

After some experiences I found that problem was in version of npgsql driver. With version - 3.2.7 all is Ok.

And also I had observed, that updates from PostgreSQL database is more stable through ODBC driver.

With npgsql I have problems with connection sometime, and also with connection during the automatic update from gateaway.