pg_restore parallel from machine with more CPUs than the server... bad?

From: Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
To: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: pg_restore parallel from machine with more CPUs than the server... bad?
Date: 2021-06-13 16:24:50
Message-ID: CAOC+FBX2bDfuf5bm0=+81ij9yeJMNh+tESREm_Bv6sqpFYbvZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

I have an AWS RDS instance with 4 CPU. I have a EC2 instance I fired up
with 16 CPU thinking I could pg_restore --jobs 16 and it would be great,
and my restore ground to a halt with a bunch of locks on refreshing
materializing views about 600GB into ~700GB.

I was wondering if there was any risk associated with restoring on a
computer with more CPU than the destination server (and indeed using more
CPU than the server)?

--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Vijaykumar Jain 2021-06-13 16:42:01 Re: pg_restore parallel from machine with more CPUs than the server... bad?
Previous Message Wells Oliver 2021-06-13 16:16:00 Re: pg_restore: warning: invalid creation date in header