Skip to content
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

Fix broken link in anatomy-of-locks-reduce.mdx #348

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

hasegeli
Copy link

@hasegeli hasegeli commented Jan 23, 2025

Very nice article @gulcin!

I noticed your link is broken.

@gulcin
Copy link
Contributor

gulcin commented Jan 26, 2025

@hasegeli thank you so much, glad you liked it!

The URLs are deliberately promoting to pgroll.com as it is our new website for pgroll project and we'd like to get some more traffic there. Thanks for reporting the broken link, I will replace it with the correct one (https://pgroll.com/blog/anatomy-of-table-level-locks-in-postgresql).

@@ -14,7 +14,7 @@ canonicalUrl: https://pgroll.com/blog/anatomy-of-table-level-locks-reducing-lock
ogImage: https://raw.githubusercontent.com/xataio/mdx-blog/main/images/[email protected]
---

I've started blogging about [Anatomy of table-level locks in PostgreSQL](https://pgroll.com/posts/anatomy-of-table-level-locks-in-postgresql). In the first [blog](https://pgroll.com/posts/anatomy-of-table-level-locks-in-postgresql), we've talked about why database systems use locking mechanisms and how Postgres utilizes MVCC to avoid most concurrency issues, reducing the necessity for locks. We then talked about DDL locks and explained how the Postgres lock queue works.
I've started blogging about [Anatomy of table-level locks in PostgreSQL](anatomy-of-locks). In the first blog post, we've talked about why database systems use locking mechanisms and how Postgres utilizes MVCC to avoid most concurrency issues, reducing the necessity for locks. We then talked about DDL locks and explained how the Postgres lock queue works.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've started blogging about Anatomy of table-level locks in PostgreSQL. In the first blog post, we've talked about why database systems use locking mechanisms and how Postgres utilizes MVCC to avoid most concurrency issues, reducing the necessity for locks. We then talked about DDL locks and explained how the Postgres lock queue works.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hasegeli we intentionally keep the URLs referring to pgroll.com to increase traffic to our new website dedicated to pgroll project.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood. Feel free to edit or close this PR.

@gulcin gulcin self-assigned this Jan 26, 2025
@gulcin gulcin added the bug Something isn't working label Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants