Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bnLfb-0002zB-Mg for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Sep 2016 08:17:19 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bnLfb-0003kM-9P for pgadmin-hackers@arkaria.postgresql.org; Fri, 23 Sep 2016 08:17:19 +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 1bnLfb-0003kG-0j for pgadmin-hackers@postgresql.org; Fri, 23 Sep 2016 08:17:19 +0000 Received: from mail-it0-x234.google.com ([2607:f8b0:4001:c0b::234]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bnLfY-0001rf-D6 for pgadmin-hackers@postgresql.org; Fri, 23 Sep 2016 08:17:18 +0000 Received: by mail-it0-x234.google.com with SMTP id 186so8639245itf.0 for ; Fri, 23 Sep 2016 01:17:16 -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=94T8rb3PcFcxg9NrT5b7J/W5TbFFuPdAVTAUo3NQExc=; b=KvbIGkT1M9tEZytUP4HFY5gKkn8vuFjfmtftDS1CFtqhrxD+dE75uKA6HQzXp+Sj6o 8daC/1nbvVHR/WXmxBZM0EWWfl2OYaJJ5efu7vtdnSUk7bYwhmC15BUV+bWylXa2lCLU BWgBlSFVTXgOiiJmVKBPpMtFCcFx2abDxH56wHiBMT7lZwZS/eIzQXhb61sUP72emEeK l0CyF7PeKED3ffN7qHnFNALAliflFi2gnaSD8ehEmyGJk48c2fmrU5GXrj5zIth2KGjP 7JbN0dpQOCa/GNkQwosv/rvyRT58IUeG6fIPwNVFvu2iQqEOoIrmeaYidF39+BWSjup5 Ebog== 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=94T8rb3PcFcxg9NrT5b7J/W5TbFFuPdAVTAUo3NQExc=; b=IeupV+fzHcaPKuNaTDsQt9oqE30nUedIQMnxxozJ21Ye/6UbkPJl0hBbPCdp+9sNDO kM4iZCKeynTmHaAaPJ0WuJpAXlIvD2nKpFym/fvEDrh402NdIlpemmHh+aGpWyUwYGAd SXshbRiWkTb+bMutZzkgFrLjDF4nz7G4WeHYKRPhDySv3HP86gMMgbuTPrY5+mhQ4Mf4 VKB1+EDcC3ZnvjpYPt4jjkIdSdLJSlfrLS1ZbHeHOnMDUj7d8GkBlaS38/OOU0IHPpTq k9acYWCkLWtg+zAh9E//TQ/P1CyraGqrPTjJhXQkKKa/gWNfxaZnLb2OJyJ0y3HA6XHZ LABw== X-Gm-Message-State: AA6/9RloRo7Hu/tYU6GzzAT8ke9J7oksUEI5n50IqDC//0c2R0menaV7opzMAJIz65hfHIdK/P3jLktYSkoqGQ== X-Received: by 10.36.242.2 with SMTP id j2mr1759113ith.108.1474618634898; Fri, 23 Sep 2016 01:17:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.1.203 with HTTP; Fri, 23 Sep 2016 01:17:14 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Fri, 23 Sep 2016 09:17:14 +0100 Message-ID: Subject: Re: [pgAdmin4][Patch]: Background process executor won't run(in case of Backup, restore) in Windows only To: Surinder Kumar Cc: pgadmin-hackers Content-Type: text/plain; charset=UTF-8 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 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. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers