Sent bit early, You can run 'VACUUM FULL VERBOSE' in query tool and verify the populated messages (pgAdmin3 vs. pgAdmin4).
On Mon, Feb 26, 2018 at 9:48 PM, Murtuza Zabuawala < murtuza.zabuaw...@enterprisedb.com> wrote: > Hi Khushboo/Dave, > > With given commit, I'm again seeing the issue raised in > https://redmine.postgresql.org/issues/1523 :( > > > > > -- > Regards, > Murtuza Zabuawala > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > > On Mon, Feb 26, 2018 at 7:49 PM, Dave Page <dp...@pgadmin.org> wrote: > >> Ensure we pick up the messages from the current query and not a previous >> one. Fixes #3094 >> >> Branch >> ------ >> master >> >> Details >> ------- >> https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdif >> f;h=08b3ccc01a4d57e8ea3657f8882a53dcd1b99386 >> Author: Khushboo Vashi <khushboo.va...@enterprisedb.com> >> >> Modified Files >> -------------- >> web/pgadmin/utils/driver/abstract.py | 1 + >> web/pgadmin/utils/driver/psycopg2/__init__.py | 64 >> +++++++++------------------ >> 2 files changed, 21 insertions(+), 44 deletions(-) >> >> >
