Two-Phase Commit
Posted4 months agoActive4 months ago
docs.pgdog.devTechstory
skepticalnegative
Debate
25/100
Distributed DatabasesTwo-Phase CommitTransaction Management
Key topics
Distributed Databases
Two-Phase Commit
Transaction Management
Discussion about the limitations and potential drawbacks of two-phase commit in distributed databases.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
22m
Peak period
1
0-1h
Avg / period
1
Key moments
- 01Story posted
Sep 10, 2025 at 1:35 PM EDT
4 months ago
Step 01 - 02First comment
Sep 10, 2025 at 1:56 PM EDT
22m after posting
Step 02 - 03Peak activity
1 comments in 0-1h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 10, 2025 at 2:52 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45201046Type: storyLast synced: 11/17/2025, 6:11:43 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
"Two-phase commit provides an eventual consistency guarantee only. While the transaction is committed, even if no errors occur, other clients will be able to see partial updates to the database cluster."
Plus, I wonder whether they have resilient mechanism to not hold transactions in the prepared state for too long, in case of crashes. In most cases, you can redesign your app/system to no require such complex things
> you can redesign your app/system
You generally don't want to do that if you can avoid it. Also, easy to make a mistake there while 2pc is pretty deterministic.