ProvSQL SQL API
Adding support for provenance and uncertainty management to PostgreSQL databases
Loading...
Searching...
No Matches

Create a times (product) gate from multiple provenance tokens. More...

Topics

 Circuit introspection
 Evaluate provenance using a compiled (built-in) semiring.

Functions

ANYELEMENT provenance_evaluate_compiled (UUID token, REGCLASS token2value, TEXT semiring, ANYELEMENT element_one)
 Evaluate provenance using a compiled (built-in) semiring.
ANYELEMENT provenance_evaluate (UUID token, REGCLASS token2value, ANYELEMENT element_one, REGTYPE value_type, REGPROC plus_function, REGPROC times_function, REGPROC monus_function, REGPROC delta_function)
 Evaluate provenance over a user-defined semiring (PL/pgSQL version).
ANYELEMENT aggregation_evaluate (UUID token, REGCLASS token2value, REGPROC agg_function_final, REGPROC agg_function, REGPROC semimod_function, ANYELEMENT element_one, REGTYPE value_type, REGPROC plus_function, REGPROC times_function, REGPROC monus_function, REGPROC delta_function)
 Evaluate aggregate provenance over a user-defined semiring (PL/pgSQL version).
ANYELEMENT provenance_evaluate (UUID token, REGCLASS token2value, ANYELEMENT element_one, REGPROC plus_function, REGPROC times_function, REGPROC monus_function=NULL, REGPROC delta_function=NULL)
 Evaluate provenance over a user-defined semiring (C version).
ANYELEMENT aggregation_evaluate (UUID token, REGCLASS token2value, REGPROC agg_function_final, REGPROC agg_function, REGPROC semimod_function, ANYELEMENT element_one, REGPROC plus_function, REGPROC times_function, REGPROC monus_function=NULL, REGPROC delta_function=NULL)
 Evaluate aggregate provenance over a user-defined semiring (C version).

Detailed Description

Create a times (product) gate from multiple provenance tokens.

Functions for evaluating provenance circuits over semirings, both user-defined (via function references) and compiled (built-in).

Filters out NULL and one-gates; returns gate_one() if all tokens are trivial, or a single token if only one remains.

Before creating an ordinary gate, the times-canonical address of the surviving multiset – uuid5('times-canonical{sorted tokens}') – is probed: the reachability rewriter pre-creates there, for self-join conjunctions of reachability tokens, a certified equivalent (the all-members-reachable circuit; see plant_reach_cover). Ordinary creation never writes under that recipe, so a hit is always a deliberate plant; the ordinary order-dependent recipe is used otherwise, so ordinary times gates (and their formula rendering) are untouched.

Source code
provsql.sql line 1063

Create a monus (difference) gate from two provenance tokens

Implements m-semiring monus. Returns token1 if token2 is NULL (used for LEFT OUTER JOIN semantics in the EXCEPT rewriting).

Source code
provsql.sql line 1112

Create a project gate for where-provenance tracking

Records the mapping between input and output attribute positions.

Parameters
tokenchild provenance token
positionsarray encoding attribute position mappings
Source code
provsql.sql line 1154

Create an equijoin gate for where-provenance tracking

Parameters
tokenchild provenance token
pos1attribute index in the first relation
pos2attribute index in the second relation
Source code
provsql.sql line 1181

Create a plus (sum) gate from an array of provenance tokens

Filters out NULL and zero-gates; returns gate_zero() if all tokens are trivial, or a single token if only one remains. Before creating a gate, probes the canonical address of the multiset – a dedicated v5 recipe namespace over the sorted tokens (plus is commutative), in which this function never creates anything, so a gate found there is always a deliberate pre-creation computing the same sum. That is the bounded-hop reachability route's hook: it plants, at the canonical address of a vertex's per-length tokens, a certified gate over its native within-bound circuit, keeping the natural hop-discarding query on the linear evaluation route. Absent a canonical gate, the ordinary order-dependent recipe is used, so ordinary plus gates (and their formula rendering) are untouched.

Source code
provsql.sql line 1212

Driver for provenance over recursive queries (WITH RECURSIVE).

Invoked by the planner hook (lower_recursive_cte in provsql.c) when it lowers a recursive CTE whose body touches provenance-tracked relations. The hook deparses the CTE body to SQL and calls this function, which runs naive bottom-up (fixpoint) evaluation: each round re-evaluates the body base UNION recursive over a tracked working table until the provenance tokens stop changing. Every round goes through ProvSQL's normal rewriting, so the recursive join yields times gates, the untracked base branch yields gate_one, and the UNION yields the plus merge of alternative derivations – no provenance is plumbed by hand here. The result is left in a tracked temp table named work_name, which the hook then scans in place of the CTE.

The working tables (work_name and a scratch _new) are created once and reused across rounds (TRUNCATE + INSERT), so the round count never accumulates relation locks. Because content-addressed gate UUIDs make structurally identical sub-circuits share, the fixpoint test is an exact relational EXCEPT and the circuit stays the shared (polynomial) form.

Scope: UNION (set) recursion. On acyclic input the structural fixpoint is reached and the resulting circuit is the universal provenance, sound for any semiring. On cyclic input the circuit never stabilises structurally; when the session's provenance class (provsql.provenance) is 'absorptive' or 'BOOLEAN' we instead stop at the value-fixpoint bound (number of derivable tuples) – every minimal, tuple-repetition-free derivation is then covered, and the longer ones are absorbed in any absorptive semiring (after Deutch, Milo, Roy & Tannen, ICDT 2014) – and wrap the resulting tokens in the 'absorptive' assumption marker, so that non-absorptive semiring evaluations (counting, why-provenance: genuinely infinite on cyclic data) refuse them while probability, Boolean, formula-as-circuit and min-plus evaluations proceed. Under the general classes, cyclic input trips the max_iter guard.

This function has no SET search_path on purpose: body_sql is the caller's deparsed query and must resolve relation names in the caller's path.

Parameters
body_sqlthe recursive CTE body, e.g. 'SELECT 1 UNION SELECT e.dst FROM edge e JOIN reach r ON e.src=r.node'
work_namethe working relation name body_sql references (the CTE name)
colnamescomma-separated user columns, e.g. 'node'
coldefcolumn definitions for the working table, e.g. 'node INTEGER'
max_itersafety bound on fixpoint rounds (non-termination guard)
Source code
provsql.sql line 1301

Create a comparison gate for HAVING clause provenance

Parameters
left_tokenprovenance token for the left operand
comparison_opOID of the comparison operator
right_tokenprovenance token for the right operand
Source code
provsql.sql line 1408

Create an arithmetic gate over scalar-valued provenance children

Builds a deterministic gate_arith from an operator tag and an ordered list of children. The tag is one of the provsql_arith_op ENUM values declared in src/provsql_utils.h (PLUS=0, TIMES=1, MINUS=2, DIV=3, NEG=4) and is stored in the gate's info1 field. Children must be UUIDs of scalar-producing gates (gate_rv, gate_value, or another gate_arith). The token UUID is derived deterministically from op and children so identical sub-expressions share their gate.

Parameters
opOperator tag (provsql_arith_op).
childrenOrdered list of child gate UUIDs.
Returns
UUID of the (possibly pre-existing) gate_arith.
Source code
provsql.sql line 1451

Functions for evaluating provenance circuits over semirings, both user-defined (via function references) and compiled (built-in).

Function Documentation

◆ aggregation_evaluate() [1/2]

ANYELEMENT update_provenance::aggregation_evaluate ( UUID token,
REGCLASS token2value,
REGPROC agg_function_final,
REGPROC agg_function,
REGPROC semimod_function,
ANYELEMENT element_one,
REGPROC plus_function,
REGPROC times_function,
REGPROC monus_function = NULL,
REGPROC delta_function = NULL )

Evaluate aggregate provenance over a user-defined semiring (C version).

Source code
provsql.sql line 1657

◆ aggregation_evaluate() [2/2]

ANYELEMENT update_provenance::aggregation_evaluate ( UUID token,
REGCLASS token2value,
REGPROC agg_function_final,
REGPROC agg_function,
REGPROC semimod_function,
ANYELEMENT element_one,
REGTYPE value_type,
REGPROC plus_function,
REGPROC times_function,
REGPROC monus_function,
REGPROC delta_function )

Evaluate aggregate provenance over a user-defined semiring (PL/pgSQL version).

Handles agg and semimod gates produced by GROUP BY queries.

Parameters
tokenprovenance token to evaluate
token2valuemapping table from tokens to semiring values
agg_function_finalfinalization function for the aggregate
agg_functionaggregate combination function
semimod_functionsemimodule scalar multiplication function
element_oneidentity element of the semiring
value_typeOID of the semiring value type
plus_functionsemiring addition
times_functionsemiring multiplication
monus_functionsemiring monus, or NULL
delta_functionδ-semiring operator, or NULL
Source code
provsql.sql line 1657

◆ provenance_evaluate() [1/2]

ANYELEMENT update_provenance::provenance_evaluate ( UUID token,
REGCLASS token2value,
ANYELEMENT element_one,
REGPROC plus_function,
REGPROC times_function,
REGPROC monus_function = NULL,
REGPROC delta_function = NULL )

Evaluate provenance over a user-defined semiring (C version).

Optimized C implementation of provenance_evaluate. Infers the value type from element_one. Monus and delta functions are optional.

Parameters
tokenprovenance token to evaluate
token2valuemapping table from tokens to semiring values
element_oneidentity element of the semiring
plus_functionsemiring addition (aggregate)
times_functionsemiring multiplication (aggregate)
monus_functionsemiring monus, or NULL if not needed
delta_functionδ-semiring operator, or NULL if not needed
Source code
provsql.sql line 1519

◆ provenance_evaluate() [2/2]

ANYELEMENT update_provenance::provenance_evaluate ( UUID token,
REGCLASS token2value,
ANYELEMENT element_one,
REGTYPE value_type,
REGPROC plus_function,
REGPROC times_function,
REGPROC monus_function,
REGPROC delta_function )

Evaluate provenance over a user-defined semiring (PL/pgSQL version).

Recursively walks the provenance circuit and evaluates each gate using the provided semiring operations. This is the generic version that accepts semiring operations as function references.

Parameters
tokenprovenance token to evaluate
token2valuemapping table from tokens to semiring values
element_oneidentity element of the semiring
value_typeOID of the semiring value type
plus_functionsemiring addition (aggregate)
times_functionsemiring multiplication (aggregate)
monus_functionsemiring monus (binary), or NULL
delta_functionδ-semiring operator, or NULL
Source code
provsql.sql line 1519

◆ provenance_evaluate_compiled()

ANYELEMENT update_provenance::provenance_evaluate_compiled ( UUID token,
REGCLASS token2value,
TEXT semiring,
ANYELEMENT element_one )

Evaluate provenance using a compiled (built-in) semiring.

This C function handles semiring evaluation entirely in C++ for better performance. The semiring is specified by name.

Parameters
tokenprovenance token to evaluate
token2valuemapping table from tokens to semiring values
semiringname of the compiled semiring (e.g., "formula", "counting")
element_oneidentity element of the semiring
Source code
provsql.sql line 1494