Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gN1AL-0003Cg-Eb for pgsql-admin@arkaria.postgresql.org; Wed, 14 Nov 2018 19:49:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gN1AI-0006vz-Bu for pgsql-admin@arkaria.postgresql.org; Wed, 14 Nov 2018 19:49:30 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gN1AH-0006iD-WB for pgsql-admin@lists.postgresql.org; Wed, 14 Nov 2018 19:49:30 +0000 Received: from p3plsmtpa07-02.prod.phx3.secureserver.net ([173.201.192.231]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gN1AB-0004ID-2r for pgsql-admin@lists.postgresql.org; Wed, 14 Nov 2018 19:49:28 +0000 Received: from [192.168.1.10] ([99.233.155.158]) by :SMTPAUTH: with ESMTPSA id N1A8gG5i1Ib4VN1A8gcXh9; Wed, 14 Nov 2018 12:49:21 -0700 To: pgsql-admin@lists.postgresql.org From: Simon White Organization: dCipher Computing Subject: Automating pg_Dump on Windows 2016 Server Message-ID: Date: Wed, 14 Nov 2018 14:49:18 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-CA X-CMAE-Envelope: MS4wfKtcXNNUU69wLhV9CbdqBUHernYCdq96umrwmccnHkZ2Ob3jQtw3VdOO1/v7q15qj6s0plXXyylBsZuHy2pLH3uFP3JJC+kGQnS7DRBgWXnBltwuXNsV Ag5l4udVpkrIALz3/HQrFOLoMG61qUoMNM/1cC8zcQQK/p5fPkNXOfGwt4A2EQofmHLAEqLixiZ09jeGDRpCo5vP9S3LxdMJXlo= List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi Automating pg_dump seems to be unnecessarily difficult from Windows Server 2016.  I have tried using the PGPASSWORD environment variable and the PGPASSFILE environment variable all to no avail.  The result is that I am always prompted for a password.  Could you not create a option to pass the password on the command line or the location of a password file to be used. That certainly would make things simpler. Since I was using the "postgres" user I tried setting the password under the "postgres" user in pgAdmin4 but that did not help either. -- Regards, Simon White dCipher Computing 705-500-0191