On Mon, Dec 23, 2013 at 7:19 AM, Mike Williams <mike.williams@xxxxxxxxxx> wrote:
How can restoring a database with a lot of large objects run faster?
It seems that each "SELECT pg_catalog.lo_create('xxxxx');" is run
independently and sequentially, despite having --jobs=8 specified.
I don't have an answer for why the restore seems to be serialized, but have you considered creating your pg_dump (-Fc) but exclude all the lobs, then dump or COPY the large objects out separately which you can them import with a manually-specified number of processes? By "manually specified", I mean execute a number of COPY FROM commands using separate threads.
