Hello Running it with format "directory" produced something I cannot import form the host application. So I aborted that.
Running it now and recording with Instruments. Guess I'll have to leave it cooking for the full procedure but I've added an initial one to pastebin. https://pastebin.com/QHRYUQhb Sent this with screenshot attached first but don't think the list supports that... So here's a screenshot from instruments after running for a few mins. https://www.dropbox.com/s/3vr5yzt4zs5svck/pg_dump_profile.png?dl=0 Cheers -- Henrik Cednert cto | compositor Filmlance International On 21 Nov 2017, at 19:46, Tom Lane <t...@sss.pgh.pa.us<mailto:t...@sss.pgh.pa.us>> wrote: Robert Haas <robertmh...@gmail.com<mailto:robertmh...@gmail.com>> writes: On Tue, Nov 21, 2017 at 12:01 PM, Tom Lane <t...@sss.pgh.pa.us<mailto:t...@sss.pgh.pa.us>> wrote: Can you get a profile of where the machine is spending its time during the dump run? On Linux I'd recommend "perf", but on macOS, hmm ... You could use Activity Monitor, but as far as I can see that just captures short-duration snapshots, which might not be representative of a 10-hour run. XCode's Instruments feature would probably be better about giving a full picture, but it has a steep learning curve. macOS's "sample" is pretty easy to use and produces text format output that is easy to email. Ah, good idea. But note that only traces one process, so you'd need to first determine whether it's pg_dump or the backend that's eating most of the CPU. Or sample both of them. regards, tom lane
