dependabot[bot] opened a new pull request, #2795: URL: https://github.com/apache/datafusion-sqlparser-rs/pull/2795
Bumps [pg_query](https://github.com/pganalyze/pg_query.rs) from 6.2.1 to 18.1.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pganalyze/pg_query.rs/blob/main/CHANGELOG.md">pg_query's changelog</a>.</em></p> <blockquote> <h2>18.1.0 2026-10-27</h2> <ul> <li>Upgrade to Postgres 18.6 (libpg_query 18.1.0) <ul> <li>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.</li> <li>Robustness: overly deep queries now return a "stack depth limit exceeded" error instead of crashing the process (<a href="https://redirect.github.com/pganalyze/libpg_query/pull/348">#348</a>), and the deparser strictly checks unexpected pointer values in input parse trees instead of crashing</li> <li>Parser: comments are now ignored when parsing queries (they are only significant for scanning), fixing parse errors for tokens like <code>NOT /* comment */ IN</code> (<a href="https://redirect.github.com/pganalyze/libpg_query/pull/378">#378</a>); PL/pgSQL statements without bodies now return an error instead of crashing (<a href="https://redirect.github.com/pganalyze/libpg_query/pull/363">#363</a>)</li> <li>Parser: PL/pgSQL parsing reworked to use proper type definitions (Postgres 18.0.0), replacing the previous ad-hoc approach</li> <li>Deparser: parentheses are now added based on operator precedence, fixing cases where deparsed SQL changed meaning or was invalid (<a href="https://redirect.github.com/pganalyze/libpg_query/pull/371">#371</a>)</li> <li>Deparser: comment handling reworked for Postgres 18 multi-statement strings: comments between statements are no longer attributed to the following statement (relevant for <code>deparse_comments_for_query</code>)</li> <li><code>normalize</code>: support <code>NOTIFY</code> statements (<a href="https://redirect.github.com/pganalyze/libpg_query/pull/340">#340</a>) and fix handling of <code>U&</code> special constants in <code>DefElem</code> nodes (<a href="https://redirect.github.com/pganalyze/libpg_query/pull/347">#347</a>)</li> <li><code>summary</code>: fix a relation going missing when a CTE shares its name (<a href="https://redirect.github.com/pganalyze/libpg_query/pull/367">#367</a>) and fix a memory leak when the tree walk throws an error</li> </ul> </li> <li><strong>Breaking</strong>: <code>parse</code>, <code>fingerprint</code> and <code>summary</code> now require parser/fingerprint options arguments, corresponding to the C <code>pg_query_parse_opts</code>, <code>pg_query_fingerprint_opts</code> and <code>pg_query_summary</code> APIs. Options accept <code>ParserOptions</code>/<code>FingerprintOptions</code> constants or raw integers; pass <code>0</code> for the defaults: <ul> <li><code>parse(statement, parser_options)</code></li> <li><code>fingerprint(statement, parser_options, fingerprint_options)</code></li> <li><code>summary(statement, parser_options, truncate_limit)</code></li> </ul> </li> <li><strong>Breaking</strong>: <code>deparse</code> now requires a <code>DeparseOptions</code> argument, and all <code>deparse</code> convenience methods (<code>ParseResult::deparse</code>, <code>protobuf::ParseResult::deparse</code>, <code>Node::deparse</code>, <code>NodeEnum::deparse</code>, <code>NodeRef::deparse</code>, <code>NodeMut::deparse</code>) likewise require it, mirroring the C <code>PostgresDeparseOpts</code> struct (comments, pretty_print, indent_size, max_line_length, trailing_newline, commas_start_of_line); pass <code>Default::default()</code> for the previous plain behavior</li> <li>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</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pganalyze/pg_query.rs/commit/20f3a182dc74ef0406752548bc6fb79fbfb591b1"><code>20f3a18</code></a> Release 18.1.0 (<a href="https://redirect.github.com/pganalyze/pg_query.rs/issues/79">#79</a>)</li> <li>See full diff in <a href="https://github.com/pganalyze/pg_query.rs/compare/v6.2.1...v18.1.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
