Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eqLZK-0001XZ-Lu for pgadmin-hackers@arkaria.postgresql.org; Mon, 26 Feb 2018 16:24:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1eqLZJ-0001rl-F4 for pgadmin-hackers@arkaria.postgresql.org; Mon, 26 Feb 2018 16:24:01 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eqLZJ-0001ra-6P for pgadmin-hackers@lists.postgresql.org; Mon, 26 Feb 2018 16:24:01 +0000 Received: from mail-oi0-x242.google.com ([2607:f8b0:4003:c06::242]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eqLZE-00022e-QI for pgadmin-hackers@postgresql.org; Mon, 26 Feb 2018 16:23:59 +0000 Received: by mail-oi0-x242.google.com with SMTP id x10so8500085oig.2 for ; Mon, 26 Feb 2018 08:23:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IElRbv/Egh7jEU/ANYEn/ysQuXr3rcPu8OrlUff6CSQ=; b=urTZ8ncdWKRyQOxZaulVArErHm5CPC9RB0+EkQPmZRnBlBe5VInzZFgaVpbBif9uw+ 5R+vxSlbVU5lkrPgq793dWpEH2D9L1ZDyutFRq5z4EcHil4Wzv3maOmKp0eUAfoi2iLS 60IVWGypSl5WPcZ6QdOb/OaAo+nEV5ffcZBc0R1K+XiypaBfG8xSC3ZVKX9QYk2hFov7 vdyAyZ9LCKcPV7t001qy3FdfAARGx1YP+9ETQiZtZfq/hzrmAXWDSXDx9tTL63DjCjj7 IXTKqvCkWQj4eutagsW0FknO11QO6/GyCgKXL9jc31iOAbT73Lry0vbhbBksWR1A2WQ5 /5lQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IElRbv/Egh7jEU/ANYEn/ysQuXr3rcPu8OrlUff6CSQ=; b=XsA9M8aeJkWhlXlUYPEyCWOj5PTxsKvXq1SorAbjKncm2mj8QSgilpaW0J65lHyCSN j+tCYtT+U5twsB/27BobE9qrEIl0UYPoeouq4BgIWMmGzPFo8yoG0IXY2yn8ry5TQM+J 8uXQMU7skhgC10s6HI9MyaxWX9oCuZ6hUt84sRFgCtRSh2SyQlc8i1Tc3Ulg2rEtZqib bPtxBAltkuRHyXaHUMM1zah2bbXme4wBxMORNldf/LMTAZsJFqc9+Q6+lKI9lJ/YkD8e IJNchvVoG8agNWj/GHvsgzBlB8E3GbC90e7EKJwH5C+YdGU5n+sm+YuyIfsVb/91moeM p6bA== X-Gm-Message-State: APf1xPAaw18l1e+LQZZtWLW1ImkE/21AZNQS4ijVJxusap3w0dfyL1yo HmYEHPNPYEsb4ReTxs+MZO/Xeh57G+CZG4+0BCbqIg== X-Google-Smtp-Source: AG47ELuhRPGj0YaMLLaLWLvVjTEZaFehQdRhWOiVhA+/AbaB8uHgPVDb1JmWBFjz6Zf+7joFJULExTlbdmHyDOv4fH0= X-Received: by 10.202.95.215 with SMTP id t206mr7167328oib.264.1519662235704; Mon, 26 Feb 2018 08:23:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.8.150 with HTTP; Mon, 26 Feb 2018 08:23:35 -0800 (PST) In-Reply-To: References: From: Murtuza Zabuawala Date: Mon, 26 Feb 2018 21:53:35 +0530 Message-ID: Subject: Re: pgAdmin 4 commit: Ensure we pick up the messages from the current query To: Dave Page , Khushboo Vashi Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="001a113cd072bd07bd05661fef54" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a113cd072bd07bd05661fef54 Content-Type: text/plain; charset="UTF-8" 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.zabuawala@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 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 >> >> Modified Files >> -------------- >> web/pgadmin/utils/driver/abstract.py | 1 + >> web/pgadmin/utils/driver/psycopg2/__init__.py | 64 >> +++++++++------------------ >> 2 files changed, 21 insertions(+), 44 deletions(-) >> >> > --001a113cd072bd07bd05661fef54 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sent bit early,=C2=A0
<= br>
You can run 'VACUUM FULL VERBOSE' in query tool and verify th= e populated messages (pgAdmin3 vs. pgAdmin4).=C2=A0


On Mon, Feb 26, 2018 at 9:48 PM, Murtuza= Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:
= Hi Khushboo/Dave,

With given commit, I'm again seeing the issue raised in = ht= tps://redmine.postgresql.org/issues/1523 :(




=
--=
Regards,
Murtuza Zabuawala
EnterpriseDB:=C2=A0http://www.= enterprisedb.com
The Enterprise PostgreSQL Company

<= /div>

On Mon, Feb 26, 2018 at 7:49 PM, Dave Page <= span dir=3D"ltr"><dpage@pgadmin.org> wrote:
Ensure we pick up the messages from the current query an= d not a previous one. Fixes #3094

Branch
------
master

Details
-------
https://git.postgresql.org/gitweb?p=3Dpgadmin4.git;a=3Dcom= mitdiff;h=3D08b3ccc01a4d57e8ea3657f8882a53dcd1b99386
Author: Khushboo Vashi <khushboo.vashi@enterprisedb.com>

Modified Files
--------------
web/pgadmin/utils/driver/abstract.py=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= |=C2=A0 1 +
web/pgadmin/utils/driver/psycopg2/__init__.py | 64 +++++++++----------= --------
2 files changed, 21 insertions(+), 44 deletions(-)



--001a113cd072bd07bd05661fef54--