Re: BUG #13684: pg_restore does not restore indexes when --jobs=X passed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: cdaringe(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13684: pg_restore does not restore indexes when --jobs=X passed
Date: 2015-10-16 20:37:44
Message-ID: 30563.1445027864@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

cdaringe(at)gmail(dot)com writes:
> I have read the documentation on pg_restore using --jobs. Unfortunately,
> when I run the pg_restore command with --jobs=4 or --jobs=6, it _skips_
> re-adding indexes to my tables.

It seems pretty unlikely that it would just "skip" them. More probable
is that the index creation commands are failing for some reason. Have
you looked at pg_restore's output and/or the postmaster log for clues?

If that doesn't turn up any info, can you provide a self-contained
test case?

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message 許耀彰 2015-10-16 23:26:45 postgresql table data control
Previous Message l 2015-10-16 20:30:31 BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby