Contents

• Changelog
  • 0.4.9 – 2026-10-09
  • 0.4.8 – 2026-10-09
  • 0.4.7 – 2026-10-09
  • 0.4.6 – 2026-10-08
  • 0.4.5 – 2026-10-08
  • 0.4.4 – 2026-10-06
  • 0.4.3
  • 0.4.2
  • 0.4.1 and earlier

Changelog

Versions are released on PGXN. Each upgrade script (pg_grammar_guard--OLD--NEW.sql) documents, in its own header, exactly what changed and why; that is the authoritative per-version record.

0.4.9 – 2026-10-09

No behavior change; names inside function bodies are English. The internal _reglas() and _correlacionado() are _rules() and _correlated(); the generated grammars are byte-identical.

0.4.8 – 2026-10-09

The Medium and Low findings of the external audit of 0.4.5 left open, each measured on 0.4.7 first (test/audit.sh: every tooth red there with its control green).

• GG-08: a correlated pivot with no values is refused; it compiled to root ::=.
• GG-10: never a NULL grammar. A NULL value, a field without a name or a NULL pivot made the grammar NULL, which a client reads as “unconstrained”. Refused.
• GG-11: grammar_fingerprint(grammar_field[]) hashes the canonical JSON; separators inside a value and dropped NULLs made two grammars share a fingerprint. A stored one changes once.
• GG-12: catalog_tables() no longer lists other sessions' temporary tables, which let any role with TEMP make a whole-database watch read broken.
• GG-13: a spec that comes out NULL is broken, through pg_living_assertions 0.5.9, which this version requires.
• GG-14: the spec resolves with its author’s path. watch() kept its own, so an unqualified name ignored the author’s schema and could only resolve in pg_temp.
• GG-15: max_items is at most 1000, and a value that is not a whole number is a clear error.
• GG-16: an enum of 40,000 values builds in linear time; it took 10 s.
• GG-17: a NULL dialect is refused.
• GG-18: duplicate field names, an empty name, a non-boolean required and non-string values are refused.
• GG-05 (whoever may run a check may insert a row in its history) stays as it is: the fix the audit suggests, a SECURITY DEFINER run(), would stop checks from running as their author. Since pg_living_assertions 0.5.9 such a row is dated by the server and lasts until the next honest check. GG-07 is closed in pg_living_assertions 0.5.9.

0.4.7 – 2026-10-09

From an external audit of 0.4.5, each finding measured on 0.4.6 before it was changed (test/audit.sh, make check-audit, in make check-suites: every tooth red on 0.4.6 with its control green).

• GG-01: a grammar_guard schema someone else created is refused. CREATE EXTENSION used it silently, and its owner’s to_json(text) ran in place of pg_catalog’s as whoever called – a superuser, measured. The install refuses a schema owned by a role that is neither the installer nor a superuser, and every function searches pg_catalog first.
• GG-02: a table with capitals is its own table. catalog_tables() returned names unquoted, so "Customers" was read back as customers: the grammar offered another table’s columns, and drift in "Customers" read holds. Names are quoted identifiers now; lower-case names come out as before.
• GG-04: catalog_tables() is ordered by schema and name. ORDER BY 1 inside an aggregate orders by a constant, so the list followed pg_class’s physical order and churn or a restore read as drift. A watch approved over catalog_tables() may read broken once after the upgrade, if it was approved with another order; the upgrade names those watches. Re-approve the ones that do.
• GG-03: a watch runs as the role that declared it, through pg_living_assertions 0.5.8, which this version requires (the tooth is red against 0.5.7).
• test/cluster.sh loads pg_living_assertions from LIVING_ASSERTIONS_DIR when set.

0.4.6 – 2026-10-08

• Metadata only. The PGXN description is two sentences now; the longer explanation it carried is in this README. No code changed: the upgrade script 0.4.5 -> 0.4.6 changes no object.

0.4.5 – 2026-10-08

• A temporary table of the session that evaluates a grammar can no longer hide that the catalog drifted. catalog_columns(), catalog_tables() and catalog_enum() read pg_attribute, pg_class and pg_enum without a schema, and no function here named pg_temp, which PostgreSQL then searches first for tables: a temporary pg_attribute – a copy of the real one minus a new column – made the live catalog read as the approved one. That matters when the evaluation runs in someone else’s session with the owner’s rights – a SECURITY DEFINER function that runs the assertion watch() declared, as pg_agent_gate does inside an agent’s commit (an agent allowed DDL can keep such a copy). Measured on 0.4.4 (test/pg_temp.sh, make check-pgtemp): an unapproved column read broken, and holds with that copy. Every function now names pg_temp last. No table changes.

0.4.4 – 2026-10-06

• License: Apache License 2.0, replacing the PostgreSQL License, from this release on. Every version up to and including 0.4.3, already published, stays under the PostgreSQL License it was released with. No code changed.

0.4.3

Completes the copyright and licensing files: the copyright holder’s full legal name in LICENSE and README, and a per-file SPDX header on every SQL source file. No schema change.

0.4.2

No schema change. Adds project governance and legal files (NOTICE, AUTHORS, SECURITY, CONTRIBUTING, TRADEMARK). The database objects are byte-for-byte those of 0.4.1; the 0.4.1--0.4.2 upgrade is empty on purpose.

0.4.1 and earlier

See the header of each pg_grammar_guard--*--*.sql upgrade script and the release notes on PGXN.