Repository navigation
[Mocha] Require transaction for Postgres outbox publishes - #10555
Merged
Merged
Conversation
Contributor
Patch coverage100.0% of changed lines covered (21/21)
Project coverage: 59.0% (311318/527659 lines) |
tobias-tengler
force-pushed
the
tte/outbox-require-transaction
branch
from
October 16, 2026 11:21
8601620 to
7a44401
Compare
tobias-tengler
force-pushed
the
tte/outbox-require-transaction
branch
from
October 16, 2026 11:23
7a44401 to
5dd6c4a
Compare
tobias-tengler
marked this pull request as ready for review
October 16, 2026 11:23
PascalSenn
approved these changes
Oct 19, 2026
This was referenced Oct 25, 2026
Merged
This was referenced Oct 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publishing or sending through the PostgreSQL outbox without an active transaction inserts the message immediately, independently of a later EF Core save. The message can therefore be dispatched even when the business changes fail or are never committed.
This PR requires a database or ambient transaction for outbox publishes and sends by default, while preserving runtime replies and faults and providing a named
PostgresOutboxOptions.RequireTransactionopt-out for existing nontransactional callers.