Hi
Thanks for the update.
Fahar, can you test this scenario please, and log an issue as appropriate?
On Wed, Jan 23, 2019 at 5:49 PM Petr Fedorov <petr.fedorov@phystech.edu> wrote:
>
> Hello,
>
> I managed to resolve the issue by re-creation of server node in pgAdmin4's browser. It seems that pgAdmin kept
somewherelocally 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 and re-installed pgAdmin4 v.3.6
fromthere 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
removedin Release 11 as described here 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
letme 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?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company