-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding information about involved lock levels of pg_squeeze
execution
#5278
Comments
@CC-Hsu Can you clarify what lock information you would like to see added? I assume you're talking about the "Controlling impact on other backends" section in the Using pg_squeeze documentation. The "Controlling impact" section mentions the need for an exclusive lock. Do you know what type of lock? Is it ACCESS EXCLUSIVE? Or maybe you want other information about locks that may be required while using pg_squeeze. If so, I would need more information. Thanks. |
Hi, dwicinas, I hope to know what exactly operations are allowed on a table during For example, which operations will block I try to search in the main source code It would be great if such information can be provided as table like below in the section you mentioned Controlling impact on other backends (I am not sure the correctness of the below table; this is just an example).
|
@shruthikc-gowda Hello. @nidhibhammar suggests you might be able to answer CC's questions (see above). Or, if you can't answer them, perhaps you can suggest who can answer this type of query. Thanks. |
@dwicinas, I will go through the pg_squeeze code to collect the required information. I will post the information here once it is available. |
Hi @dwicinas and @CC-Hsu, please find the requested information
@nidhibhammar, there is one update needed for "Using pg_squeeze" section Registering a table for regular processing The above sentence should be updated to Let me know if the above change can be done part of this issue itself? |
Hi, shruthikc-gowda, Thanks a lot for such clear explanation. 😄 Both pieces of texts are very important for introducing this tool to EDB customers. Thanks again. |
@CC-Hsu and @shruthikc-gowda, I've incorporated the new information into the documentation for pg_squeeze. See this topic: https://deploy-preview-5464--edb-docs-staging.netlify.app/docs/pg_extensions/pg_squeeze/using/. There I added an introductory section describing the locks and revised the first sentence in the "Registering" section. You can also look at PR 5464. |
Hi, dwicinas, Thanks a lot for your work. The information is clear to me to understand. Best Regards. |
Summary
Hi, Team,
I read through the new extension documentation page,
but I find no detailed lock level information during different execution phase of
pg_squeeze
.It would be great if the documentation can include detailed lock modes involved, so that users can clearly compared with the documentation page.
https://www.postgresql.org/docs/current/explicit-locking.html
Best Regards.
Where would you like to see this added?
https://github.com/EnterpriseDB/docs/blob/main/advocacy_docs/pg_extensions/pg_squeeze/using.mdx
Rationale
No response
The text was updated successfully, but these errors were encountered: