Skip to content

Bump pg_query from 6.2.1 to 18.1.0 in /fuzz - #2795

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/fuzz/pg_query-18.1.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/fuzz/pg_query-18.1.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Bumps pg_query from 6.2.1 to 18.1.0.

Changelog

Sourced from pg_query's changelog.

18.1.0 2026-10-27

  • Upgrade to Postgres 18.6 (libpg_query 18.1.0)
    • Performance: libpg_query now uses upb instead of protobuf-c for serialization, which is substantially faster thanks to its built-in arena allocation, resulting in 2x faster runtime.
    • Robustness: overly deep queries now return a "stack depth limit exceeded" error instead of crashing the process (#348), and the deparser strictly checks unexpected pointer values in input parse trees instead of crashing
    • Parser: comments are now ignored when parsing queries (they are only significant for scanning), fixing parse errors for tokens like NOT /* comment */ IN (#378); PL/pgSQL statements without bodies now return an error instead of crashing (#363)
    • Parser: PL/pgSQL parsing reworked to use proper type definitions (Postgres 18.0.0), replacing the previous ad-hoc approach
    • Deparser: parentheses are now added based on operator precedence, fixing cases where deparsed SQL changed meaning or was invalid (#371)
    • Deparser: comment handling reworked for Postgres 18 multi-statement strings: comments between statements are no longer attributed to the following statement (relevant for deparse_comments_for_query)
    • normalize: support NOTIFY statements (#340) and fix handling of U& special constants in DefElem nodes (#347)
    • summary: fix a relation going missing when a CTE shares its name (#367) and fix a memory leak when the tree walk throws an error
  • Breaking: parse, fingerprint and summary now require parser/fingerprint options arguments, corresponding to the C pg_query_parse_opts, pg_query_fingerprint_opts and pg_query_summary APIs. Options accept ParserOptions/FingerprintOptions constants or raw integers; pass 0 for the defaults:
    • parse(statement, parser_options)
    • fingerprint(statement, parser_options, fingerprint_options)
    • summary(statement, parser_options, truncate_limit)
  • Breaking: deparse now requires a DeparseOptions argument, and all deparse convenience methods (ParseResult::deparse, protobuf::ParseResult::deparse, Node::deparse, NodeEnum::deparse, NodeRef::deparse, NodeMut::deparse) likewise require it, mirroring the C PostgresDeparseOpts struct (comments, pretty_print, indent_size, max_line_length, trailing_newline, commas_start_of_line); pass Default::default() for the previous plain behavior
  • Fingerprint values changed: fingerprinting now follows Postgres 18 query ID behavior. In SELECT/DML statements the relation alias (if present) replaces the relation name and schema names are ignored; sequences of 2+ digits

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Nov 2, 2026
Bumps [pg_query](https://github.com/pganalyze/pg_query.rs) from 6.2.1 to 18.1.0.
- [Changelog](https://github.com/pganalyze/pg_query.rs/blob/main/CHANGELOG.md)
- [Commits](pganalyze/pg_query.rs@v6.2.1...v18.1.0)

---
updated-dependencies:
- dependency-name: pg_query
  dependency-version: 18.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/cargo/fuzz/pg_query-18.1.0 branch from 3f7ccc1 to f623f7a Compare November 9, 2026 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants