From: | Andrey Klychkov <aaklychkov(at)mail(dot)ru> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, artem(dot)lebedev <artem(dot)lebedev(at)ediweb(dot)com> |
Subject: | Re[2]: PGAdmin 4 don't refresh server info after restarting |
Date: | 2019-02-19 20:39:54 |
Message-ID: | 1550608794.489424457@f347.i.mail.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> You should report this on a pgAdmin mailing list rather than a
> PostgreSQL mailing list.
Hi, of course, I made a mistake. Thank you for showing me
>Вторник, 19 февраля 2019, 19:41 +03:00 от Robert Haas <robertmhaas(at)gmail(dot)com>:
>
>On Mon, Feb 18, 2019 at 1:20 AM Andrey Klychkov < aaklychkov(at)mail(dot)ru > wrote:
>> Hello,
>> We've noticed that pgadmin 3.x / 4.x doesn't refresh server info like server version after restarting. It makes people confused.
>> For example,
>> 1. PgAdmin was rinning
>> 2. We upgraded postgres from 11.1 to 11.2
>> 3. PgAdmin was restarted
>> 4. We continued to see 11.1
>> 5. We must push "Disconnect from server" and connect again for updating server version.
>>
>> It would be convenient that PgAdmin checks server info from time to time, at least, when PgAdmin was restarted.
>
>You should report this on a pgAdmin mailing list rather than a
>PostgreSQL mailing list.
>
>--
>Robert Haas
>EnterpriseDB: http://www.enterprisedb.com
>The Enterprise PostgreSQL Company
--
Regards,
Andrew K.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-02-19 20:39:56 | Re: propagating replica identity to partitions |
Previous Message | Julien Rouhaud | 2019-02-19 20:21:42 | Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name |