| From: | Simon White <simonwhite(at)dciphercomputing(dot)com> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Automating pg_Dump on Windows 2016 Server |
| Date: | 2018-11-14 19:49:18 |
| Message-ID: | c2e04be9-3bbb-a575-190b-c8733efaaad1@dciphercomputing.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2018-11-14 21:59:17 | Re: Automating pg_Dump on Windows 2016 Server |
| Previous Message | Rui DeSousa | 2018-11-14 16:24:54 | Re: PostgreSQL 10.5 : Logical replication timeout results in PANIC in pg_wal "No space left on device" |