Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bnM4K-0004H0-LC for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Sep 2016 08:42:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bnM4J-0007LF-Oq for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Sep 2016 08:42:51 +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 1bnM4J-0007L9-DR for pgadmin-hackers@postgresql.org; Fri, 23 Sep 2016 08:42:51 +0000 Received: from mail-io0-x22e.google.com ([2607:f8b0:4001:c06::22e]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bnM4G-0002IF-D5 for pgadmin-hackers@postgresql.org; Fri, 23 Sep 2016 08:42:50 +0000 Received: by mail-io0-x22e.google.com with SMTP id m79so111823638ioo.3 for ; Fri, 23 Sep 2016 01:42:48 -0700 (PDT) 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=NdUqcvV/0h96vaDMgARpRzps5OsAMUjo6697ckIRkV4=; b=gBajK4ZMCBZxY0UUs37E5IQ6ROmBoYL1dCsSyFSzSJabwCMmHuehuYVziFvxrC5Rmp qrls3gnzW+IgC8oFMZkg1+gElAZjpwsOUCQrovosTYjWhIQDjT/CqhN46ET9RKlAP0AT v6MJYavMRD9GBiRPnFcagVuUM2NH9cYzZoy+snTZX4n8WrZZg6IopTXJb9/9Yh9JP4ju QKeD/VydITwqhcoIDLY5EeWwUUD8bsuY/Hy9ngqvWB/eZTJ5iPA7uBhQ2InIhETRvPiF g4RRGGdM2Z6NhlYXo8OW61y2nnKRa/BbwLBPadwHAPSuokOv1uprUM9oD1N/rM/mGFNY L52A== 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=NdUqcvV/0h96vaDMgARpRzps5OsAMUjo6697ckIRkV4=; b=EMeC9lgGp8Xpq4jSR8HQ1fDoM1rS7c3TuMZ/aiLQyI+00p6R29pv7KNrTFv4E4EXJ/ d7CKwQKGK2QCFtl3VAGzccNWn4BZZY1QBvxuH5pwloWYqMFDNj5pSvGJRRBmITV8Q/pz +p1D9zErMjJhkSOrcYDR5uW0GvUWRt/Fvgv9N81wdC9SqtmZK5xTHtRbgR/zL4IlmUsw qiNigQjmCjLvdXHXNvdDm5jsu4rC95n0xeLaNHsT8lyqF/YCrnKVDiX/IbEAzbVkI6G+ aCZd7Nxl8xlOGQA9AMkGfFSRGI5h1vLzuJNBr+8QP9lc42lx2xE4uCitbJIBbwJHjOwK o04g== X-Gm-Message-State: AA6/9RkN0WoEv1QCCAssThG+L9/jP7hI2MfMSFXmg+MOLd2TB9rflRVF1m+IVPJtSraIvRZYMHLzNkLXkR6SCI5G X-Received: by 10.107.35.209 with SMTP id j200mr7631136ioj.26.1474620166512; Fri, 23 Sep 2016 01:42:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.50.212 with HTTP; Fri, 23 Sep 2016 01:42:26 -0700 (PDT) In-Reply-To: References: From: Ashesh Vashi Date: Fri, 23 Sep 2016 14:12:26 +0530 Message-ID: Subject: Re: [pgAdmin4][Patch]: Background process executor won't run(in case of Backup, restore) in Windows only To: Dave Page Cc: Surinder Kumar , pgadmin-hackers Content-Type: multipart/alternative; boundary=001a1141b946343f4e053d28c317 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 --001a1141b946343f4e053d28c317 Content-Type: text/plain; charset=UTF-8 On Fri, Sep 23, 2016 at 1:54 PM, Dave Page wrote: > > > On Fri, Sep 23, 2016 at 9:18 AM, Ashesh Vashi < > ashesh.vashi@enterprisedb.com> 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. > If we set the PYTHON INTERPRETER to run the background process. i.e. BG_PYTHON_INTERPRETER=c:\Python27\pythonw.exe We can avoid showing the flashing command window. I came to this conclusion, because - I tried to hide them using certain flags, but - it wasn't working well. -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company *http://www.linkedin.com/in/asheshvashi* > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > --001a1141b946343f4e053d28c317 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Fri, Sep 23, 2016 at 1:54 PM, Dave Page <dpage@pgadmin.org>= wrote:



= On Fri, Sep 23, 2016 at 9:18 AM, Ashesh Vashi <ashesh.vashi@en= terprisedb.com> wrote:
On Fri, Sep 23, 2016 at 1:47 PM, Dave Page <dpage@p= gadmin.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't want a command window flashing up unnecessarily.
If we set the PYTHON INTERPRETER to run the bac= kground process.
i.e. BG_PYTHON_INTERPRETER=3Dc:\Python27\pythonw= .exe

We can avoid showing the flashing command win= dow.
I came to this conclusion, because - I tried to hide them us= ing certain flags, but - it wasn't working well.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA:=C2=A0Enterprise PostgreSQL Company


http://www.linkedin.com/in/ashes= hvashi

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

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Compa= ny

--001a1141b946343f4e053d28c317--