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 1ek7Gf-0004uu-Oz for pgadmin-hackers@arkaria.postgresql.org; Fri, 09 Feb 2018 11:55:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ek7Ge-0004xi-RE for pgadmin-hackers@arkaria.postgresql.org; Fri, 09 Feb 2018 11:55:00 +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.84_2) (envelope-from ) id 1ek7Ge-0004xY-Dg for pgadmin-hackers@lists.postgresql.org; Fri, 09 Feb 2018 11:55:00 +0000 Received: from mail-wr0-x244.google.com ([2a00:1450:400c:c0c::244]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ek7Gb-0003I0-6v for pgadmin-hackers@postgresql.org; Fri, 09 Feb 2018 11:54:59 +0000 Received: by mail-wr0-x244.google.com with SMTP id 41so7948374wrc.9 for ; Fri, 09 Feb 2018 03:54:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=v98ZbXRkyit26+3pAMByCIHb3Sp5QY2m7w/pkJR/k68=; b=N6jBDL7pJd/nP8zva8HIU/pav3PQmLvuhJGE8bENwJo3Oq6vQncUYebj3JeXFbjlIn iDnNnfME2veph8HeK5d7xEoCQqc8AWC85vt6+6ybcychXo++MddKomgGCkR9drZDtqjV cbRxPlM/1nwzWeYgmChCuIOaVnPGCNpN9uySvsOiqI/N1N3aCqqNZfbfSUtsTvi4dNT9 atwle1HMLU1gfL53Xm5v7kohOR1v03kuvMSKen7QXs20u6l8xikldsHvJPzlnAkM+HB5 7SVlNVDN9QKDjHUtwF5bTWM6dZy/uABSmSM8AQc83j+QUK4rAZ2TD71jDp3hD7xEk75r LKxA== 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=v98ZbXRkyit26+3pAMByCIHb3Sp5QY2m7w/pkJR/k68=; b=CJhW23sKdz4cBy+f85nqz5TWBezfj8OeD65doLY3QcKlX3tFKWVCDoZJrz088z3TeK OtDnav24Nr0FGSg8Q+lc+r2zRD1qlSRR+/GjvH5s7X7OiYb6r3gjxL/1Nl1U4Y2DH5t0 1vRzdZLP4h33VqfWIJXHUp/TK1x9xlkOkCk9PNzWXuQSI7WMIFxsABupzhPJQtb6rGfO 03FCFiu890k6mZUGHCTILY3pVe0CxKNQpo1rVYm6XSQUYYAl82YU3k0VN3Cdb2UfgiL8 KlIPbzQoUDfp5pWNT3oUxDGResMDyE/tV2sNOvN9bpQZ7miy8fehKjtRBB64RPisv798 Q6HA== X-Gm-Message-State: APf1xPCNYo0Ta+zwC+6IK9nJeaGFKF+S9lqKXnm+SmxcEgy3sjoqXroB 0wIZaz/v/0XZcIxvFmRvKy5E3xbz3qnobih/9IM3Mg== X-Google-Smtp-Source: AH8x224guaudPhIVfg92LX2oFRkkgGf40HyV6wmABgILuwbsoC2sgPDvqWbxbrfEpJsviNT5AVgmt1RDc59wMmm5XIk= X-Received: by 10.223.151.53 with SMTP id r50mr2176187wrb.207.1518177295509; Fri, 09 Feb 2018 03:54:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.16.138 with HTTP; Fri, 9 Feb 2018 03:54:54 -0800 (PST) In-Reply-To: References: From: Dave Page Date: Fri, 9 Feb 2018 11:54:54 +0000 Message-ID: Subject: Re: [pgadmin][patch] [GreenPlum] When user press Explain Plan and Explain analyze plan an error is displayed To: Joao De Almeida Pereira Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="f403045d5a6067bda50564c63244" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --f403045d5a6067bda50564c63244 Content-Type: text/plain; charset="UTF-8" Thanks, patches applied. On Fri, Feb 2, 2018 at 10:50 PM, Joao De Almeida Pereira < jdealmeidapereira@pivotal.io> wrote: > Hi Hackers, > This is quite a big patch in order to solve the problem with the Explain > Plan. > > We sent 2 patches that have the following: > *- update-javascript-packages.diff * > Add package: > is-docker to select a specific setting when running the Chrome tests > in > Docker > > Upgrade the version of: > - babel-loader > - extract-text-webpack-plugin > - jasmine-core > - jasmine-enzyme > - moment > *- explain-plan-greenplum.diff* > Extract SQLEditor.execute and SQLEditor._poll into their own files and > add test around them > Extract SQLEditor backend functions that start executing query to their > own files and add tests around it > Move the Explain SQL from the front-end and now pass the Explain plan > parameters as a JSON object in the start query call. > Extract the compile_template_name into a function that can be used by > the different places that try to select the version of the template and the > server type > > > Thanks > Joao > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --f403045d5a6067bda50564c63244 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks, patches applied.
<= br>
On Fri, Feb 2, 2018 at 10:50 PM, Joao De Alme= ida Pereira <jdealmeidapereira@pivotal.io> wrote:=
Hi Hackers,
This is= quite a big patch in order to solve the problem with the Explain Plan.

We sent 2 patches that have the following:
= -=C2=A0update-javascript-packages.diff=C2=A0
=C2= =A0 =C2=A0 Add package:
=C2=A0 =C2=A0 =C2=A0is-docker to sele= ct a specific setting when running the Chrome tests in
=C2=A0 =C2= =A0 =C2=A0Docker

=C2=A0 =C2=A0 Upgrade the version= of:
=C2=A0 =C2=A0 - babel-loader
=C2=A0 =C2=A0 - extra= ct-text-webpack-plugin
=C2=A0 =C2=A0 - jasmine-core
=C2= =A0 =C2=A0 - jasmine-enzyme
=C2=A0 =C2=A0 - moment
-=C2=A0explain-plan-greenplum.diff
=C2=A0 Extract SQLEdi= tor.execute and SQLEditor._poll into their own files and add test around th= em
=C2=A0 Extract SQLEditor backend functions that start executin= g query to their own files and add tests around it
=C2=A0 Move th= e Explain SQL from the front-end and now pass the Explain plan parameters a= s a JSON object in the start query call.
=C2=A0 Extract the compi= le_template_name into a function that can be used by the different places t= hat try to select the version of the template and the server type


Thanks
Joao



--
Dave Page
Blog: = http://pgsnake.bl= ogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com<= br>The Enterprise PostgreSQL Company
--f403045d5a6067bda50564c63244--