reliar-store-postgres 0.9.0

PostgreSQL provider for the Reliar transactional outbox and inbox: migrations, migrate(), enqueue and the SKIP LOCKED claim.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

//! [`PostgresOutboxStore`]: construction, `enqueue`, and the `OutboxStore`/`OutboxEnqueue`/
//! `OutboxDeadLetters` implementations — two layers, mirroring `inbox/`'s shape, one file per
//! public trait (`docs/architecture/store-postgres-layout.md` Part II §6). The **store layer** (`outbox_store`, the
//! type/construction/shared helpers plus the *whole* `OutboxStore` impl; `outbox_store_dead_letters`
//! for `OutboxDeadLetters`; `outbox_store_enqueue` for `OutboxEnqueue`) holds every `Session::run`,
//! `map_err`, span, the shortfall `warn`, and the composition of several concern calls (poison
//! sweep + claim; purge's three sweeps; fail's two batches). The **concern layer** (`claim`,
//! `outcomes`, `purge`, `dead_letters`, `enqueue`) holds one `sqlx::query*!` per function, over
//! `impl PgExecutor<'_>` plus a `<Verb><Noun>Params`, and imports no `Session`, no settings, no
//! typed error, no `tracing`. `enqueue.rs` has no `crate::inbox` counterpart: the inbox has no
//! caller-transaction write side.

mod claim;
mod dead_letters;
mod enqueue;
mod error;
mod outbox_store;
mod outbox_store_dead_letters;
mod outbox_store_enqueue;
mod outcomes;
mod purge;

pub use error::{EnqueueError, PostgresOutboxError};
pub use outbox_store::PostgresOutboxStore;