| From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | pg_restore & locks |
| Date: | 2021-06-13 15:37:34 |
| Message-ID: | CAOC+FBVt9Nf=xjfCWz4PEPRqWo0_Lgma7+k+5jKdzLOhiBVCJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-06-13 15:57:17 | Re: pg_restore: warning: invalid creation date in header |
| Previous Message | Tom Lane | 2021-06-13 15:13:29 | Re: pg_restore: warning: invalid creation date in header |