| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Viral Shah <viralshah009(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rene Romero Benavides <rene(dot)romero(dot)b(at)gmail(dot)com>, "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: pg_dump fails when a table is in ACCESS SHARE MODE |
| Date: | 2020-05-02 01:24:53 |
| Message-ID: | CAKFQuwbETSv7wgxqtN-7mHvonwbWAF_P3UW2z38b+biWG=RTpw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Friday, May 1, 2020, Viral Shah <viralshah009(at)gmail(dot)com> wrote:
>
> Now, this does explain why I need to increase the max_transaction_locks so
> that I can account for all the locks pg_locks is running into while pg_dump
> is in progress. I am still trying to understand why
> pg_get_statisticsobjdef() creates locks (AccessShare) on all the base
> tables at once leading to this issue?
>
You are dumping your entire database as a consistent point-in-time whole -
how would that be doable without locking every data containing relation is
the database?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Jackson | 2020-05-04 15:36:42 | Re: Table/log file name which store the queries which got executed in last 1 month |
| Previous Message | Viral Shah | 2020-05-02 01:06:23 | Re: pg_dump fails when a table is in ACCESS SHARE MODE |