Re: Failing Multi-Job Restores, Missing Indexes on Restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Cea Stapleton <cea(at)healthfinch(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org, eli(at)healthfinch(dot)com
Subject: Re: Failing Multi-Job Restores, Missing Indexes on Restore
Date: 2016-09-29 13:09:16
Message-ID: 5266.1475154556@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Cea Stapleton <cea(at)healthfinch(dot)com> writes:
> Were using pg_restore (PostgreSQL) 9.5.4 for the restores. Weve used variations on the job number:
> /usr/bin/pg_restore -j 6 -Fc -O -c -d DBNAME RESTORE_FILE

OK ... do you actually need the -c, and if so why?

> Well take a look at the memory overcommit - would that also explain the index issues we were seeing before we were seeing the crashes?

Unlikely. I'm guessing that there's some sort of race condition involved
in parallel restore with -c, but it's not very clear what.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jeff Janes 2016-09-29 18:03:16 Re: Multiple-Table-Spanning Joins with ORs in WHERE Clause
Previous Message Cea Stapleton 2016-09-29 12:56:43 Re: Failing Multi-Job Restores, Missing Indexes on Restore