Hi,thank you very much for your help, indeed it looks like a problem with signed/unsigned values. I'll stay with 4.10 meanwhile.Best regards,HolgerGesendet: Mittwoch, 04. September 2019 um 12:27 Uhr
Von: "Aditya Toshniwal" <aditya.toshniwal@enterprisedb.com>
An: "Holger Kopp-Musick" <hkopp@gmx.de>
Cc: "pgadmin-support lists.postgresql.org" <pgadmin-support@lists.postgresql.org>, "Khushboo Vashi" <khushboo.vashi@enterprisedb.com>
Betreff: Re: Re: Negative values for obj_id: SELECT statements throwing errors in query editorHi,I had raised the concern on psycopg2 (https://github.com/psycopg/psycopg2/issues/661#issuecomment-527739621) and looks like it is a bug in pyscopg2.We need wait psycopg2 now to get this fixed.On Wed, Sep 4, 2019 at 12:50 PM Holger Kopp-Musick <hkopp@gmx.de> wrote:Hi,
thank you very much for your advice, I have attached the log. As proposed I've replaced the original file and restarted the server, yet unfortunately I'm still unable to get any results for any simple statement (ie SELECT * FROM table). In my understanding the obj_id is anyhow faulty since there are no negative values of attrelid in pg_attribute. Running the statement primary_keys.sql with the proper value returns the requested row (table.id).
Thanks,
Holger
> Please try to replace the \web\pgadmin\tools\sqleditor\templates\sqleditor\sql\default\primary_keys.sql file with the attached file and do not forget to take a backup of the original file.
> Restart the server and check the issue gets resolved or not.--Thanks and Regards,Aditya ToshniwalSoftware Engineer | EnterpriseDB India | Pune"Don't Complain about Heat, Plant a TREE"