Re: pg_restore & locks - Mailing list pgsql-admin

From Wells Oliver
Subject Re: pg_restore & locks
Date
Msg-id CAOC+FBU_XMidH-xnECxbT-e8aEwQwkX+DHFu9ghcGoL7SZL1nQ@mail.gmail.com
Whole thread Raw
In response to pg_restore & locks  (Wells Oliver <wells.oliver@gmail.com>)
List pgsql-admin
I should add all of the locks are REFRESH MATERIALIZED VIEW... statements.

On Sun, Jun 13, 2021 at 8:37 AM Wells Oliver <wells.oliver@gmail.com> wrote:
Is it normal for a parallel pg_restore to result in locks? Will these usually resolve themselves?

The restore is running with 16 jobs into an RDS instance and at the moment pg_locks has about 243 AccessShareLock, 35 ExclusiveLock, 24 AccessExclusiveLock, and 8 ShareLock...

Will these just resolve as queries finish, or is it a concern? The restore has been running a long time.

pg_restore command:

time pg_restore \
--host=${HOST} \
--user=postgres \
--format=directory \
--dbname=${DB} \
--jobs ${JOBS} \ 

Where JOBS here 16.
--


--

pgsql-admin by date:

Previous
From: Wells Oliver
Date:
Subject: Re: pg_restore: warning: invalid creation date in header
Next
From: Tom Lane
Date:
Subject: Re: pg_restore: warning: invalid creation date in header