Re: pg_restore & locks

From: Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
To: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pg_restore & locks
Date: 2021-06-13 16:03:04
Message-ID: CAOC+FBU_XMidH-xnECxbT-e8aEwQwkX+DHFu9ghcGoL7SZL1nQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)oliver(at)gmail(dot)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.
> --
> Wells Oliver
> wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
>

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2021-06-13 16:12:25 Re: pg_restore: warning: invalid creation date in header
Previous Message Wells Oliver 2021-06-13 16:02:41 Re: pg_restore: warning: invalid creation date in header