Re: Browser in pgAdmin4 v3.6 is not able to show either Function or Trigger function in Release 11 database

Поиск
Список
Период
Сортировка
От Fahar Abbas
Тема Re: Browser in pgAdmin4 v3.6 is not able to show either Function or Trigger function in Release 11 database
Дата
Msg-id CAJFwRrPa0WLwZdBeShx7rRDp44SmMyTYj9YVG1r3CXOwp9163g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Browser in pgAdmin4 v3.6 is not able to show either Function orTrigger function in Release 11 database  (Dave Page <dpage@pgadmin.org>)
Список pgadmin-support
Hi Petr,

 The issue is not reproducible with pgAdmin4 4.1 version:

Can you please perform following steps for upgrade scenario and let us know?
1)
Upgrade Scenario:
----

1. yum clean all
2. yum makecache
3. yum upgrade pgadmin4*
4. If  server is already running then shutdown the server through elephant icon
5. Now Launch pgAdmin4 /usr/pgadmin4/runtime/pgAdmin4
6. And recheck the behavior

Please try fresh Scenario in case issue is still not resolved:

2)
Fresh Scenario:
---------------------

1. yum erase pgadmin4*
2.  yum clean all
3.  yum makecache
4. yum install pgadmin4*
5.  Now Launch pgAdmin4 /usr/pgadmin4/runtime/pgAdmin4

On Thu, Jan 24, 2019 at 3:28 PM Dave Page <dpage@pgadmin.org> wrote:
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 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 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 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?



--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


--
Fahar Abbas
QMG
EnterpriseDB Corporation
Phone Office: +92-51-835-8874
Phone Direct: +92-51-8466803
Mobile: +92-333-5409707
Skype ID: live:fahar.abbas
Website: www.enterprisedb.com
Вложения

В списке pgadmin-support по дате отправления:

Предыдущее
От: Patrick De Visschere
Дата:
Сообщение: Re: Change browser in MacOS
Следующее
От: Dave Page
Дата:
Сообщение: Re: Change browser in MacOS