feat(postgres): add priority queueing for commands - #237
Draft
elmaxe wants to merge 1 commit into
Draft
Conversation
Messages can implement IPriority (KnightBus.Messages) to declare an int Priority; the PostgreSql transport locks/fetches higher-priority messages first, tie-broken by message_id asc to preserve FIFO within a priority. Schema init now runs eagerly on every receiver startup (not just when a table is missing) so already-deployed queues pick up the new priority column automatically. Scoped to commands (Send/Schedule) for now; Publish (events) is unaffected.
|
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
1 participant
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.
Messages can implement IPriority (KnightBus.Messages) to declare an int Priority; the PostgreSql transport locks/fetches higher-priority messages first, tie-broken by message_id asc to preserve FIFO within a priority.
Schema init now runs eagerly on every receiver startup (not just when a table is missing) so already-deployed queues pick up the new priority column automatically. Scoped to commands (Send/Schedule) for now; Publish (events) is unaffected.
What this changes
Notes for the reviewer
Checklist
dotnet build KnightBus.slnxanddotnet testpassdotnet csharpier check .passes (CI fails on unformatted code)docs/is updated, if the change is user-visible<Version>is bumped in the affected.csprojandCHANGELOG.mdhas an entry, if thisshould be released