Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hTiZB-0001CD-D2 for pgadmin-hackers@arkaria.postgresql.org; Thu, 23 May 2019 07:55:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hTiYC-0000k6-74 for pgadmin-hackers@arkaria.postgresql.org; Thu, 23 May 2019 07:54:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hTiYB-0000iW-QR for pgadmin-hackers@lists.postgresql.org; Thu, 23 May 2019 07:54:07 +0000 Received: from mail-it1-x143.google.com ([2607:f8b0:4864:20::143]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hTiY8-0002s1-Lt for pgadmin-hackers@postgresql.org; Thu, 23 May 2019 07:54:07 +0000 Received: by mail-it1-x143.google.com with SMTP id 9so7149042itf.4 for ; Thu, 23 May 2019 00:54:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sIPzLnAGaUyGqPAUYq2nkk2FxjsfIbK0peI1gq9mVpE=; b=ZtGx09W/nx/SZaV/M294EEO9tmI6mr2wEWPaxjrL6froEdOdzdKIr+oyORwzeJR00K Pe2Z577IAZ5j2setGWfH7aW2tX2T+eItV8ioxn5VAj01VOmvxvmDorP2xpPNNI7vlWrZ fMkxcNFx31NrAmhqqknia3FzvgSQ9qaHsAq2GLaXfyP3IcDFSsfpeDSVihmt5TxLm8vB SowEzUixCIan55/jx1HVzgtcvLZApy8NJWypKgGvm8ADoE14tEAPg0Db8ZuyQld5L9kv nq7Et+qWE0YeE3HeCsuwY53N4iwHkggOFH8VkZMeTILsspDlLFzvPokAlw3LucjPQmD8 mMYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sIPzLnAGaUyGqPAUYq2nkk2FxjsfIbK0peI1gq9mVpE=; b=gYuj8K30J93j2US7I4ISGOoTCggHKUfaroiNdYZQL/jJiGFb3K9vrnAHzIBzgcLD1Q 8LVGjedS7LTLkscw56TwMgCljXchGuWpncdarEI7s7WFvEA8GCbXDEJC2CeuTYlEBGLW Fw9UUBN9tgGFAOdRYziqpKf40MeqYx5vs4zCgAZRwFIEHl1Z6sau+LLAH2cPRO7hOUZK o7j+jbTmhxhbvDi20frzlXaoNKrWhSagK00cDFZe1cFj5kq1uEoXKavh3kfO5l4+mlu9 SkVrnMJfikt3tFcgcwxiGkHwxy2/aWBBoCko2SPpGB4mih+F+iwU8k3WaD+LFatYj2s+ g87w== X-Gm-Message-State: APjAAAUoBuwL3xSFFKHhPkSEjzXnwbW0PEQ1eEq+/UANqm0qu0SJJw3k hN4GYsJoKiS5h85O6CbMgHmpfQuQiCkNV6i/dblbzA== X-Google-Smtp-Source: APXvYqxNOv6lFxpY0on7B0yJN0PeGn3PV2EfvcSKwS5MwRWbMgzhHZOG38V6ioPd9FEn9qGMTfdJIbTSsBVwi8AkSxs= X-Received: by 2002:a24:70ca:: with SMTP id f193mr11651641itc.103.1558598042205; Thu, 23 May 2019 00:54:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Thu, 23 May 2019 08:53:51 +0100 Message-ID: Subject: Re: [pgAdmin][RM4263] "Not connected to the server or the connection to the server has been closed." returned with some queries To: Aditya Toshniwal Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000a75a4505898962f0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000a75a4505898962f0 Content-Type: text/plain; charset="UTF-8" Thanks, applied. On Wed, May 22, 2019 at 6:12 AM Aditya Toshniwal < aditya.toshniwal@enterprisedb.com> wrote: > Hi Hackers, > > Attached is the quick fix for the issue. The problem was with parsing > failure of JSON result in explain plan code. I have added an api test case > to check length of result format to match with JS code expectations for > explain plan. > > Kindly review. > -- > Thanks and Regards, > Aditya Toshniwal > Software Engineer | EnterpriseDB India | Pune > "Don't Complain about Heat, Plant a TREE" > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --000000000000a75a4505898962f0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks, applied.

On Wed, May 22, 2019 at 6:12 AM Aditya Tos= hniwal <aditya.tosh= niwal@enterprisedb.com> wrote:
Hi Hackers,

Attached is the quick f= ix for the issue. The problem was with parsing failure of JSON result in ex= plain plan code. I have added an api test case to check length of result fo= rmat to match with JS code expectations for explain plan.

Kindly rev= iew.
--
Thanks and Re= gards,
Aditya Toshniwal
Softwar= e Engineer |=C2=A0EnterpriseDB India |=C2=A0Pune
"Don't Complain about Heat, Pl= ant a TREE"


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

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL = Company
--000000000000a75a4505898962f0--