Serialize concurrent datasource publications
This commit is contained in:
@@ -24,7 +24,10 @@ declared pushdown support. Live previews preserve the provider's effective row,
|
||||
serialized-byte, and elapsed-time limits and its redacted diagnostics.
|
||||
Producer modules can append a bounded tabular result or create a new static
|
||||
datasource through an idempotent capability. The publication ledger retains the
|
||||
producer run, output materialization, provenance, and replay identity.
|
||||
producer run, output materialization, provenance, and replay identity. On
|
||||
PostgreSQL, a transaction-scoped advisory lock serializes each tenant, producer,
|
||||
and idempotency identity before any output side effect, so retries from multiple
|
||||
application or worker nodes resolve to one durable publication.
|
||||
|
||||
Tabular staging also evaluates governed quality rules and classifies schema
|
||||
changes before promotion. Blocking stages remain inspectable, and successful
|
||||
|
||||
Reference in New Issue
Block a user