From: | Fabrízio de Royes Mello <fabrizio(at)timbira(dot)com(dot)br> |
---|---|
To: | Shaozhong SHI <shishaozhong(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: How to explicitly lock and unlock tables in pgsql? |
Date: | 2022-03-16 20:35:48 |
Message-ID: | CAPfkCSD+rbeZW6QKR_mhmTRqOOSd06eq+LfpDJiaMYt8LqAhVg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
Em qua., 16 de mar. de 2022 às 17:30, Shaozhong SHI <shishaozhong(at)gmail(dot)com>
escreveu:
> Table locks present a barrier for progressing queries.
>
> How to explicitly lock and unlock tables in pgsql, so that we can
> guarantee the progress of running scripts?
>
> Regards,
>
> David
>
Have a look at https://www.postgresql.org/docs/current/sql-lock.html
--
Fabrízio Mello
Consultor
fabrizio(at)timbira(dot)com(dot)br
https://www.timbira.com.br/
[image: facebook] <https://pt-br.facebook.com/Timbira/>
[image: twitter] <https://twitter.com/timbirabrasil>
[image: linkedin] <https://sg.linkedin.com/company/timbira>
[image: instagram] <https://www.instagram.com/timbirabrasil/>
From | Date | Subject | |
---|---|---|---|
Next Message | Zheng Li | 2022-03-16 21:17:18 | Re: Support logical replication of DDLs |
Previous Message | Shaozhong SHI | 2022-03-16 20:32:02 | Apparently table locks are the key issue to see red flags |
From | Date | Subject | |
---|---|---|---|
Next Message | Shaozhong SHI | 2022-03-16 20:56:47 | How to explicitly state unlock in sql? |
Previous Message | Shaozhong SHI | 2022-03-16 20:32:02 | Apparently table locks are the key issue to see red flags |