Known issues (testing)
This is a user-facing “summary”. The canonical list is: angarabook/src/operations/known-issues.md.
SQLSTATE quick reference
| SQLSTATE | Name | Context |
|---|---|---|
0A000 | feature_not_supported | Unsupported SQL forms, complex RLS predicates in IR mode, server-side predicates on client-encrypted columns (randomized), unsupported RLS mask expressions |
22023 | invalid_parameter_value | Invalid stats_level_max values, invalid SET BREAK_GLASS ... TTL=... values |
23514 | check_violation | Insert into partitioned parent with no matching child/DEFAULT partition |
25001 | active_sql_transaction | SET SESSION CONTEXT inside an active transaction |
42501 | insufficient_privilege | User/role/policy/break-glass actions without required roles, protected SQL without SecurityContext |
42809 | wrong_object_type | DML on append-only tables, disabling append-only on child while parent is append-only |
General
pg_database probe (KI-2026-001)
Some pg_database queries may lead to a stall/hang.
See details and repro: angarabook/src/operations/known-issues.md → KI-2026-001.
Checksum verification
- If on-disk page verification fails, read path fails closed with explicit
checksum mismatchdiagnostics. - Quick operator probe:
angara-cli storage verify-pages --dir <data_dir> --json
SQL behavior
Unsupported SQL forms
0A000 feature_not_supported is expected for currently out-of-scope SQL forms:
WITH RECURSIVE- Set operations (
UNION/INTERSECT/EXCEPT) - Window functions
ORDER BY ... NULLS FIRST|LAST
Partitioning
23514 check_violation is expected when inserting into a partitioned parent table and no child partition (and no DEFAULT partition) matches the row partition key.
Append-only tables
42809 wrong_object_type is expected for:
UPDATEon an append-only table,DELETEon an append-only table,- Attached child partition trying to disable append-only while parent remains append-only.
Stats parameter validation
22023 invalid_parameter_value is expected for invalid stats_level_max values outside [0..3].
Statistics
HLL NDV tracking
HLL NDV tracking for TEXT columns skips very long values (len > 256) by design.
This keeps memory and merge cost bounded for streaming stats.
Security behavior
Privilege enforcement
42501 insufficient_privilegeis expected when user/role/policy/break-glass actions are executed without required roles.22023 invalid_parameter_valueis expected for invalidSET BREAK_GLASS ... TTL=...values (missing/zero/exceeds max TTL).25001 active_sql_transactionis expected forSET SESSION CONTEXTinside an active transaction.
Session security context
42501 insufficient_privilegeis expected inscram/certmodes when protected SQL executes without a sessionSecurityContext.0A000 feature_not_supportedis expected in IR mode for unsupported complex RLS predicates (bounded fail-closed planner/IR contract).
Client encryption and RLS masks
0A000 feature_not_supportedis expected for unsupported server-side predicates on client-encrypted columns in randomized mode.0A000 feature_not_supportedis expected for unsupported RLS mask expressions outside v1 bounded forms (partial,nullify).
What’s Next
- Support and Bug Report Artifact Collection — how to report a new issue if yours is not in the list.
- Client Compatibility — which clients are tested as “works as documented”.
- SQL Compatibility Overview — which SQL constructs return
0A000and why.