Hello, I managed to resolve the issue by re-creation of server node in pgAdmin4's browser. It seems that pgAdmin kept somewhere locally that the version of the server is 10 (I did an upgrade) - so it was using wrong templates for sql queries.
23.01.2019 19:10, Petr Fedorov пишет: > > Hello! > > I'm on Centos 7 and just migrated to Release 11 (from 10) using > official repository > <https://download.postgresql.org/pub/repos/yum/11/redhat/rhel-7-x86_64/pgdg-centos11-11-2.noarch.rpm> > and re-installed pgAdmin4 v.3.6 from there too. Suddenly I'm not > able to see in browser Function and Trigger Functions! > > It appears that the problem is due to this sql request which refers to > proisagg columns which has been incompatibly removed in Release 11 as > described here > <https://www.postgresql.org/message-id/153486142520.1370.12035528830969343...@wrigleys.postgresql.org> > for example: > > SELECT pr.oid, pr.proname || '(' || > COALESCE(pg_catalog.pg_get_function_identity_arguments(pr.oid), '') || > ')' as name, lanname, pg_get_userbyid(proowner) as funcowner, > description > FROM > pg_proc pr > JOIN > pg_type typ ON typ.oid=prorettype > JOIN > pg_language lng ON lng.oid=prolang > LEFT OUTER JOIN > pg_description des ON (des.objoid=pr.oid AND > des.classoid='pg_proc'::regclass) > WHERE > proisagg = FALSE > AND pronamespace = 16626::oid > AND typname NOT IN ('trigger', 'event_trigger') > ORDER BY > proname; > > > It seems that in order to resolve it I just need to replace proisagg = > FALSE with prokind != 'a'. Could you please let me know whether I can > do it myself using pgAdmin4 version from the repository or I need to > install from the source code? > > Or is there any other workaround for that issue? >
