Conversation
|
|
||
| * CRuby 2.7 | ||
| * CRuby 3.0 | ||
| * CRuby 3.1 |
There was a problem hiding this comment.
3.0 and 3.1 is EOL, maybe in the next release, we can retire them and support 4
There was a problem hiding this comment.
I think technically 4.0 is supported now, but its not running in CI.
| - Add missing top-level postgres_deparse.h in Makefile install step | ||
| - This was an oversight from the previous 6.2.0 release |
There was a problem hiding this comment.
I think we can skip this, its not relevant to pg_query users.
| - Improve pg_query_summary function: | ||
| - Speed up summary truncate replacement logic | ||
| - Correctly handle `GRANT .. ON ALL TABLES IN SCHEMA` statements | ||
| - Correctly handle schema qualified filter columns |
There was a problem hiding this comment.
We could probably omit these, since the main news here is the addition of pg_query_summary - although that is not yet exposed in the Ruby API.
| * Upgrade to libpg_query 17-6.2.1 | ||
| - Add pg_query_is_utility_stmt function to determine if query text contains utility statements [#313](https://github.com/pganalyze/libpg_query/pull/313) | ||
| - This is a fast check for callers that don't actually need the parse tree itself | ||
| - Add fast summary information function (pg_query_summary) |
There was a problem hiding this comment.
Note that the Ruby bindings for pg_query_summary and pg_query_is_utility_stmt are still missing, so it's not really correct to include these in the changelog
There was a problem hiding this comment.
Ah good point (also re: pganalyze/pg_query_go#145 (comment)).
If we removed #344 (comment), I guess we should also have removed them 🤔
There was a problem hiding this comment.
Yeah, that's fair, we can amend the changelog to clarify this.
3 participants
No description provided.