Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bnLmy-0003GC-4L for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Sep 2016 08:24:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bnLmx-0004Zg-Gg for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Sep 2016 08:24:55 +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_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bnLmx-0004ZZ-1X for pgadmin-hackers@postgresql.org; Fri, 23 Sep 2016 08:24:55 +0000 Received: from mail-it0-x231.google.com ([2607:f8b0:4001:c0b::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bnLmu-0001y0-1b for pgadmin-hackers@postgresql.org; Fri, 23 Sep 2016 08:24:54 +0000 Received: by mail-it0-x231.google.com with SMTP id o3so8503171ita.1 for ; Fri, 23 Sep 2016 01:24:51 -0700 (PDT) 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=8vVr8ltklkkWoCDRPvvo/FvzlBykJjgNYWgsYA4Pv9s=; b=uAEyOt2pcgqG4sLxb9s392EPNaMZRvQPZ9HAn4HGIizRG0KN86/4Bpqj83636FR3h8 /fNLEFxizKUWbLvrVy0ntISjbWABtw6DaHSEL1Mf4M8y5ybMbSQb5tRnF40XV4OOjn7P Uns8pHswuUi16dnzERCgd/0EgaP5PRbrf8VFVBXhfD4P37D0GExxfXvGP/vy4Ij9Joof pFEzmIzCsdsAZ/cPc1wbg3gqnPBcXlETREVeALSpw8akQbBFJ6RxTnYQeHTYfkHhdqiH aD+/fbBJzcW0RADS+yDrogQPfeuvQRp/FtOE5JBAq88JtHG5sFs+dNse2rCZD9ztc64J ZB+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8vVr8ltklkkWoCDRPvvo/FvzlBykJjgNYWgsYA4Pv9s=; b=VPeuGrSKVt+JNuWW9pchX/tmU/4gocZmmj83lSYRS5AjsY2HTpYZqiluUbI+JTDCkm ZFHbaZtm8FDQVeebhTgWzzBcHEEfwyGTAcuxKgeFmO/+sYsUDxcOR8aoXDBvq4xukdUz nb2Luxo0L5VdOK1SbeQrkjJgtGeP3bdron14Ly0rYUAxtMGYTi58VqHPzU5T1hqTPIdQ Z8WByqTDH8SDIeMi5C0MJF+nc7kWsg+l9HNMiMYxtsqaoOB5vpvhQtAnftE65QRcY1D5 By4MF/LCYB3/6BuIfL3i4ef9oub74fiUR1htipCY4N5wF9efJCzIe7iSBTZgBOf5q3ft N+xQ== X-Gm-Message-State: AA6/9Rnk/zmyQFpNidA/DzOK5vd/q3egaN078PXijqBfYn8Gi7ByiiYfxmbOllbwgVV/lCmCkglEwDgqnX0yYg== X-Received: by 10.36.242.2 with SMTP id j2mr1787895ith.108.1474619090119; Fri, 23 Sep 2016 01:24:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.1.203 with HTTP; Fri, 23 Sep 2016 01:24:49 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Fri, 23 Sep 2016 09:24:49 +0100 Message-ID: Subject: Re: [pgAdmin4][Patch]: Background process executor won't run(in case of Backup, restore) in Windows only To: Ashesh Vashi Cc: Surinder Kumar , pgadmin-hackers Content-Type: multipart/alternative; boundary=94eb2c115a460bbaad053d2883ee X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --94eb2c115a460bbaad053d2883ee Content-Type: text/plain; charset=UTF-8 On Fri, Sep 23, 2016 at 9:18 AM, Ashesh Vashi wrote: > On Fri, Sep 23, 2016 at 1:47 PM, Dave Page wrote: > >> On Fri, Sep 23, 2016 at 5:59 AM, Surinder Kumar >> wrote: >> > Actually It doesn't broke anywhere, instead It runs successfully. On >> > debugging I found that it runs the subprocess.Popen() utility but it >> doesn't >> > run internally the pg_dump utitliy. On running the same command on >> windows >> > cmd prompt it works. >> > Then on setting parameters close_fds=False and cmd_shell=True, It works. >> > I ran backup in Google Chrome. >> >> It certainly runs pg_dump for me - I see the output in the monitoring >> dialogue, and I get a dump file at the end. >> >> I also use Chrome. >> > It may differ for different version of python. > Maybe. I'm using 2.7. Either way, I don't want a command window flashing up unnecessarily. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --94eb2c115a460bbaad053d2883ee Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Fri, Sep 23, 2016 at 9:18 AM, Ashesh Vashi <ashesh.vash= i@enterprisedb.com> wrote:
=
On Fri, Sep 23, 2016 at 1:47 PM, Dave Page &= lt;dpage@pgadmin.org= > wrote:
On Fri, Sep 23, 2016 at 5:59 AM, Surinder Kumar
<su= rinder.kumar@enterprisedb.com> wrote:
> Actually It doesn't broke anywhere, instead It runs successfully. = On
> debugging I found that it runs the subprocess.Popen() utility but it d= oesn't
> run internally the pg_dump utitliy. On running the same command on win= dows
> cmd prompt it works.
> Then on setting parameters close_fds=3DFalse and cmd_shell=3DTrue, It = works.
> I ran backup in Google Chrome.

It certainly runs pg_dump for me - I see the output in the monitorin= g
dialogue, and I get a dump file at the end.

I also use Chrome.
It may differ for different = version of python.

= Maybe. I'm using 2.7.=C2=A0

Either way, I don&= #39;t want a command window flashing up unnecessarily.

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

Enterpris= eDB UK: http://ww= w.enterprisedb.com
The Enterprise PostgreSQL Company
--94eb2c115a460bbaad053d2883ee--