Yugabyte + Docker + Postgres ERROR : System column with id -3

Answered

Hello, I have an instance of Postgres running on a Docker machine created by Yugabyte. I'm getting this Error. I know that the message say it's not supported, but I tested others clients, and works normal, why such tool like DataGrip doesn't work?

 

2
12 comments

Could you email me vasily.chernov@jetbrains.com your IDE logs?

Also, specify your PostgreSQL server version. 

As a temporary workaround you can enable "Introspect using JDBC metadata" for your data source

1

Thanks Vasily,

That really helped. 

here is the link of the meu idea log:  https://drive.google.com/file/d/1Czkw4TaUysiapuP5NnSUp9mkyWbG88nY/view?usp=sharing

1

Getting the same error with Yugabyte, the workaround helps, but not obvious.

1

Yes, it's not obvious since there is no pure support for Yugabyte solutions and Yugabyte is not pure PostgreSQL

 

1

Hi, I am using Datagrip 2021.2.4 which doesn't have that `Introspect using JDBC metadata` option. Because of this, I got the same error as the OP.

How can I solve this issue with DataGrip 2021.2.4? Where can I enable `Introspect using JDBC metadata`?

Thanks!

0

this option moved to Advanced tab.

0

Hi Yuriy, thanks for your reply! I did try to find it under Advanced tab. However there is no (exact) match for "Introspect using JDBC metadata".  

Maybe I miss something? Is there a new way to configure it? Could you help point out where this option is located? Maybe a screenshot would help. 

Thanks!

0

 which database do you work with? why do you need this option?

here it is:

1

Thanks very much, now I am able to connect to the database. (I just reinstall it and was able to find that option. Not sure why the first time I didn't see this...)

The database I connect to is YugabyteDB. I think I must use this option since YugabyteDB does not use PostgreSQL’s system columns given that these functions are handled by the DocDB storage engine of YugabyteDB. This option makes DataGrip’s PostgreSQL connector use standard JDBC metadata as opposed to PostgreSQL specific metadata.

0

There is an issue about YugabyteDB in our tracker https://youtrack.jetbrains.com/issue/DBE-8524 . Follow for progress and leave comments there.

1

Hi vasily chernov I Developer Advocate at YugabyteDB and would like to see what we can do to solve this. Reading the pseudo-columns like xmin is not supported because we have a different storage (with no vacuum problems ;). If you tell me which kind of queries are raising "with id -... is not supported yet" and what is the purpose I can check what we can do.

0

Franck Pachot,

Could you drop me an email and we can discuss it there with a responsible developer?

My email Vasily.Chernov@jetbrains.com

0

Please sign in to leave a comment.