| From: | Jayson Hreczuck <jayson(dot)hreczuck(at)studentuniverse(dot)com> |
|---|---|
| To: | Shaozhong SHI <shishaozhong(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Apparently table locks are the key issue to see red flags |
| Date: | 2022-03-17 13:21:18 |
| Message-ID: | CAHg7=h68+oRXAbmNznEJbuecC=Dyw4hMkZ21=KL=YxeB+kGv3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general pgsql-sql |
Need more detail on this. Locks are generally caused by long updates or
writes or perhaps a hung transaction. Can you reply with a bit more detail
of what you are seeing, perhaps pg_stat_activity list?
Rule of thumb for high trx environments is to batch updates especially for
larger tables to avoid excessive locking.
On Wed, Mar 16, 2022 at 4:32 PM Shaozhong SHI <shishaozhong(at)gmail(dot)com>
wrote:
>
> Apparently table locks are the key issue to see red flags.
>
> As we observe, every time, red marking occurs, there must be some tables
> are locked.
>
> Can anyone shed light into this?
>
> Regards,
>
> David
>
--
*Jayson Hreczuck | Principal Database AdministratorC: +1 617.571.9861*130
Turner St, Ste 530, Waltham, MA 02453
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2022-03-17 15:29:34 | Re: Shared postgres-cluster / permissions |
| Previous Message | Holger Jakobs | 2022-03-17 11:29:40 | Re: Shared postgres-cluster / permissions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shukla, Pranjal | 2022-03-17 14:05:07 | Re: Query on WAL Optimization and Streaming Replication |
| Previous Message | Laurenz Albe | 2022-03-17 13:19:52 | Re: Query on WAL Optimization and Streaming Replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Tu | 2022-03-18 14:46:35 | PostgreSQL trigger on user logon |
| Previous Message | Laurenz Albe | 2022-03-17 07:51:52 | Re: How to explicitly lock and unlock tables in pgsql? |