Follow up: I took the SQL generated by the backup command (visible when looking at the "More details..." of the running backup job), and ran it directly on the server, and the backup took up about a minute (rather than failing after 15 hours).
So I have a solution, but how is it that running the backup job via pgAdmin takes 1000x times longer?
Other point of interest... clicking "Stop Process" to kill the backup may take an hour or so to actually stop the process. I.e., it continues to grind away and transfer data to the local PC for a long, long time.
Cheers,
Dave
On Thu, Jan 30, 2020 at 9:21 AM Dave Caughey <caugheyd@gmail.com> wrote:
Hi all,
I'm attempting to back up some databases, but they keep failing after many hours with an "exit code: 1".
I've tried format "Plain" and "Tar". I'm using UTF8 encoding. I'm accepting all the default dump options with the exception of additionally enabling the "Include CREATE DATABASE command" setting.
I was able to generate backups for some small databases (a few hundred MB) but haven't successfully been able to get a backup of a GB-sized database.
