On Fri, Sep 23, 2016 at 1:54 PM, Dave Page <dp...@pgadmin.org> wrote:
> > > On Fri, Sep 23, 2016 at 9:18 AM, Ashesh Vashi < > ashesh.va...@enterprisedb.com> wrote: > >> On Fri, Sep 23, 2016 at 1:47 PM, Dave Page <dp...@pgadmin.org> wrote: >> >>> On Fri, Sep 23, 2016 at 5:59 AM, Surinder Kumar >>> <surinder.ku...@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 >>> 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.enterprisedb.com/> *http://www.linkedin.com/in/asheshvashi* <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 >
