pg_query 1.1.0 → 2.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0db8e898d08ff3642a800ab296d7ac10dd9556e3c5a626f005bae86d35273372
-  data.tar.gz: a869a1faeb3ae0bed9d5031f2a4d26263843fde368bfeb096c1c9f48ea30c9f8
+  metadata.gz: f5f97de1d1113193f804264c63e29434831dbec88c917471a64b93302308310e
+  data.tar.gz: fbb5024c13381a02b3706bd9366f62f2e499a8afb30f25f5dfb4ae15723ae2a6
 SHA512:
-  metadata.gz: e0f51970e5f268d9d9d32d791288db0d7a048c4880f706ff7d483b0efacd1a355600f5b8ca8a0b57b75a05cda8c7b207402bb6680fad0fdaeaf7809fab06c441
-  data.tar.gz: 6281530a32add88cd8a474a8e224e817723e288e850f9d9232aba69208b1178d89b7135d613d15800176bd611b3d6fcd0600fb48c3e8c880f6aa47f5296bae45
+  metadata.gz: a4b80ec2176046a6f6f99cb9a053f5dd5cc10dfc0bed7f98276b46088e054e33da6efb1d7e2d1fc52264b2a915d0048007b3a800507a9eb58da460bfe4bedcd3
+  data.tar.gz: 174fd09a8ee19b437d4601cfe544a8aa25cf88d6c38a1aa81814f8a59c54a4cbb0f6497d1af7fb4b8034356546f35f1841d875be3b434136c984ec0747c1e1e2

data/CHANGELOG.md

@@ -1,35 +1,146 @@
 # Changelog
 
+## 2.0.1     2021-03-18
+
+* Fix Gem spec to correctly reference include files
+  - This would have shown as a build failure when using the published `2.0.0` gem
+
+
+## 2.0.0     2021-03-18
+
+* Update to PostgreSQL 13 parser
+* Update to libpg_query v2, and new Protobuf-based format
+  * WARNING: This is a breaking change if you are directly interacting with the
+    parsetree (helpers like `table` and such still work the same way)
+* Use actual Ruby classes for parser result, instead of decoded JSON
+  * This is essentialy to enable easy and fast two-way communication with
+    the C library, and as a bonus makes for a better interaction on the Ruby
+    side, as we are handling actual objects instead of hashes and arrays.
+* Use new deparser maintained directly in libpg_query
+  * This replaces the complete Ruby deparser with a new, more complete deparser
+    that is directly maintained in libpg_query. Further deparser improvements
+    should be directly contributed to [libpg_query](https://github.com/pganalyze/libpg_query)
+* Tables helper: Return more details through "tables_with_details" method
+  * This is renamed from the previously badly named "tables_with_types"
+    method. Note that this change should not affect the output of the
+    primary "tables" helper.
+* Replace on-demand libpg_query source download with bundled source code
+  * Its unnecessary to download the source on-demand, and makes this more
+    complex than it needs to be. Instead, introduce a new "update_source" rake
+    task that can be called to refresh the source for a specified revision.
+* Re-implement smart truncation without requiring a special node type
+  * This ensures the truncate method works with the new deparser, without
+    the C level code needing to know about it. We may add it in the C library
+    in the future for edge cases that can't be covered by this slightly
+    hack-ish approach, but for now this avoids unnecessary C library
+    deparser modifications with non-standard node types.
+* Update Ruby finterprinting to new fingerprint format and XXH3 hash
+  * Note that its recommended to use PgQuery.fingerprint for performance
+    reasons, but when the tree has been modified, it can be convenient to
+    run a Ruby-side fingerprint instead of the C-based one that is faster.
+
+
+## 1.3.0     2020-12-28
+
+* Incorporate newer libpg_query updates in 10-1.0.3 and 10-1.0.4
+  * Adds support for running on ARM
+  * Fixes asprintf warning during builds
+  * Updates to newer Postgres 10 patch release (10.15)
+* Deparsing improvements by [@emin100](https://github.com/emin100)
+  * Add support for additional DROP statements (#147)
+  * Fix CREATE TABLE AS - Support without TEMP, Add ON COMMIT (#149)
+  * Empty target list support (#156)
+  * UNION parentheses (#158)
+  * OVERLAY keyword function (#161)
+  * Array indirection (#162)
+  * ARRAY functions (#163)
+  * Correctly handle column names that need escaping in INSERT and UPDATE statements (#164)
+  * INSERT INTO ON CONFLICT (#166)
+  * LATERAL JOIN (#168)
+  * UPDATE FROM clause (#170)
+  * SELECT aggregate FILTER (#175)
+  * INTERSECT operator (#176)
+* Deparsing: Improve handling of boolean type casts [@himanshu-pro](https://github.com/himanshu-pro) & [@emin100](https://github.com/emin100)
+* `tables` method: Find tables in the subquery of CREATE TABLE AS (#172) [@Tassosb](https://github.com/Tassosb)
+* Support Ruby 3.0, verify SHA256 checksum of downloaded libpg_query (#178) [@stanhu](https://github.com/stanhu)
+  * Verify SHA256 checksum to guard against any malicious attempts to change the archive
+  * Use `URI.open` to fix Ruby 3.0 support
+
+
+## 1.2.0     2019-11-10
+
+* Reduce escaped keywords to Postgres-specific keywords, and ignore unreserved keywords
+  * This matches the behaviour of Postgres' quote_identifier function, and avoids problems
+    when doing text comparisons with output involving that function
+  * Note that this will lead to different output than in earlier pg_query versions,
+    in some cases
+
+
+## 1.1.1     2019-11-10
+
+* Deparsing improvements by [@emin100](https://github.com/emin100)
+  * Deparse ILIKE, COLLATE and DISCARD (#133)
+  * CREATE CAST (#136)
+  * CREATE SCHEMA (#136)
+  * UNION, UNION ALL and EXCEPT in SELECT queries (#136)
+  * CREATE DOMAIN (#145)
+  * Subquery indirection (#157)
+  * Fix Type Cast Parentheses Problem (#152)
+  * SELECT INTO (#151)
+  * SET DEFAULT in INSERT INTO (#154)
+  * REVOKE (#155)
+  * PREPARE and EXECUTE (#148)
+  * INSERT INTO ... RETURNING (#153)
+  * Fix Alter .. RENAME SQL (#146)
+* Deparsing improvements by [@herwinw](https://github.com/herwinw)
+  * Fix subquery in COPY in deparse (#112)
+  * Function call indirection (#116)
+  * Function without parameters (#117)
+  * CREATE AGGREGATE
+  * CREATE OPERATOR
+  * CREATE TYPE
+  * GRANT statements
+  * DROP SCHEMA
+* Deparsing improvements by [@akiellor](https://github.com/akiellor)
+  * Named window functions (#150)
+* Deparsing improvements by [@himanshu](https://github.com/himanshu)
+  * Arguments in custom types (#143)
+  * Use "double precision" instead of "double" type name (#139)
+* Use explicit -z flag to support OpenBSD tar (#134) [@sirn](https://github.com/sirn)
+* Add Ruby 2.6 to Travis tests
+* Escape identifiers in more cases, if necessary
+
+
 ## 1.1.0     2018-10-04
 
 * Deparsing improvements by [@herwinw](https://github.com/herwinw)
-  * Add NULLS FIRST/LAST to ORDER BY [#95](https://github.com/lfittl/pg_query/pull/95)
-  * VACUUM [#97](https://github.com/lfittl/pg_query/pull/97)
-  * UPDATE with multiple columns [#99](https://github.com/lfittl/pg_query/pull/99)
-  * DISTINCT ON [#101](https://github.com/lfittl/pg_query/pull/101)
-  * CREATE TABLE AS [#102](https://github.com/lfittl/pg_query/pull/102)
-  * SQL value functions [#103](https://github.com/lfittl/pg_query/pull/103)
-  * LOCK [#105](https://github.com/lfittl/pg_query/pull/105)
-  * EXPLAIN [#107](https://github.com/lfittl/pg_query/pull/107)
-  * COPY [#108](https://github.com/lfittl/pg_query/pull/108)
-  * DO [#109](https://github.com/lfittl/pg_query/pull/109)
-* Ignore pg_query.so in git checkout [#110](https://github.com/lfittl/pg_query/pull/110) [@herwinw](https://github.com/herwinw)
-* Prefer __dir__ over File.dirname(__FILE__) [#110](https://github.com/lfittl/pg_query/pull/104) [@herwinw](https://github.com/herwinw)
+  * Add NULLS FIRST/LAST to ORDER BY [#95](https://github.com/pganalyze/pg_query/pull/95)
+  * VACUUM [#97](https://github.com/pganalyze/pg_query/pull/97)
+  * UPDATE with multiple columns [#99](https://github.com/pganalyze/pg_query/pull/99)
+  * DISTINCT ON [#101](https://github.com/pganalyze/pg_query/pull/101)
+  * CREATE TABLE AS [#102](https://github.com/pganalyze/pg_query/pull/102)
+  * SQL value functions [#103](https://github.com/pganalyze/pg_query/pull/103)
+  * LOCK [#105](https://github.com/pganalyze/pg_query/pull/105)
+  * EXPLAIN [#107](https://github.com/pganalyze/pg_query/pull/107)
+  * COPY [#108](https://github.com/pganalyze/pg_query/pull/108)
+  * DO [#109](https://github.com/pganalyze/pg_query/pull/109)
+* Ignore pg_query.so in git checkout [#110](https://github.com/pganalyze/pg_query/pull/110) [@herwinw](https://github.com/herwinw)
+* Prefer __dir__ over File.dirname(__FILE__) [#110](https://github.com/pganalyze/pg_query/pull/104) [@herwinw](https://github.com/herwinw)
 
 
 ## 1.0.2     2018-04-11
 
 * Deparsing improvements
-  * SELECT DISTINCT clause [#77](https://github.com/lfittl/pg_query/pull/77) [@Papierkorb](https://github.com/Papierkorb)
-  * "CASE expr WHEN ... END" clause [#78](https://github.com/lfittl/pg_query/pull/78) [@Papierkorb](https://github.com/Papierkorb)
-  * LEFT/RIGHT/FULL/NATURAL JOIN [#79](https://github.com/lfittl/pg_query/pull/79) [@Papierkorb](https://github.com/Papierkorb)
-  * SELECT that includes schema name [#80](https://github.com/lfittl/pg_query/pull/80) [@jcsjcs](https://github.com/jcsjcs)
+  * SELECT DISTINCT clause [#77](https://github.com/pganalyze/pg_query/pull/77) [@Papierkorb](https://github.com/Papierkorb)
+  * "CASE expr WHEN ... END" clause [#78](https://github.com/pganalyze/pg_query/pull/78) [@Papierkorb](https://github.com/Papierkorb)
+  * LEFT/RIGHT/FULL/NATURAL JOIN [#79](https://github.com/pganalyze/pg_query/pull/79) [@Papierkorb](https://github.com/Papierkorb)
+  * SELECT that includes schema name [#80](https://github.com/pganalyze/pg_query/pull/80) [@jcsjcs](https://github.com/jcsjcs)
 
 
 ## 1.0.1     2018-02-02
 
-* Parse CTEs and nested selects in INSERT/UPDATE [#76](https://github.com/lfittl/pg_query/pull/76) [@jcoleman](https://github.com/jcoleman)
-* Drop explicit json dependency [#74](https://github.com/lfittl/pg_query/pull/74) [@yuki24](https://github.com/yuki24)
+* Parse CTEs and nested selects in INSERT/UPDATE [#76](https://github.com/pganalyze/pg_query/pull/76) [@jcoleman](https://github.com/jcoleman)
+* Drop explicit json dependency [#74](https://github.com/pganalyze/pg_query/pull/74) [@yuki24](https://github.com/yuki24)
 
 
 ## 1.0.0     2017-10-31
@@ -50,18 +161,18 @@
 ## 0.13.4    2017-10-20
 
 * Update to libpg_query 9.5-1.7.0
-  - Fixes compilation old gcc before 4.6.0 [#73](https://github.com/lfittl/pg_query/issues/73)
+  - Fixes compilation old gcc before 4.6.0 [#73](https://github.com/pganalyze/pg_query/issues/73)
 
 
 ## 0.13.3    2017-09-04
 
-* Fix table detection for SELECTs that have sub-SELECTs without FROM clause [#69](https://github.com/lfittl/pg_query/issues/69)
+* Fix table detection for SELECTs that have sub-SELECTs without FROM clause [#69](https://github.com/pganalyze/pg_query/issues/69)
 
 
 ## 0.13.2    2017-08-10
 
-* Support table detection in sub-SELECTs in JOINs [#68](https://github.com/lfittl/pg_query/pull/65) [@seanmdick](https://github.com/seanmdick)
-* Legacy ".parsetree" helper: Fix "Between" and "In" operator does not have "AEXPR" [#66](https://github.com/lfittl/pg_query/issues/66)
+* Support table detection in sub-SELECTs in JOINs [#68](https://github.com/pganalyze/pg_query/pull/65) [@seanmdick](https://github.com/seanmdick)
+* Legacy ".parsetree" helper: Fix "Between" and "In" operator does not have "AEXPR" [#66](https://github.com/pganalyze/pg_query/issues/66)
   * For new applications please use ".tree" method which uses the native structure
     returned from libpg_query which resembles Postgres node names more closely
 
@@ -74,7 +185,7 @@
 
 ## 0.13.0    2017-07-30
 
-* Introduce split between SELECT/DML/DDL for tables method [#65](https://github.com/lfittl/pg_query/pull/65) [@chrisfrommann](https://github.com/chrisfrommann)
+* Introduce split between SELECT/DML/DDL for tables method [#65](https://github.com/pganalyze/pg_query/pull/65) [@chrisfrommann](https://github.com/chrisfrommann)
   * Backwards compatible, use the new select_tables/dml_tables/ddl_tables to
     access the categorized table references
 * Update libpg_query to 9.5-1.6.2
@@ -102,14 +213,14 @@
 
 ## 0.11.5    2017-07-09
 
-* Deparse coldeflist [#64](https://github.com/lfittl/pg_query/pull/64) [@jcsjcs](https://github.com/jcsjcs)
-* Use Integer class for checking integer instead of Fixnum [#62](https://github.com/lfittl/pg_query/pull/62) [@makimoto](https://github.com/makimoto)
+* Deparse coldeflist [#64](https://github.com/pganalyze/pg_query/pull/64) [@jcsjcs](https://github.com/jcsjcs)
+* Use Integer class for checking integer instead of Fixnum [#62](https://github.com/pganalyze/pg_query/pull/62) [@makimoto](https://github.com/makimoto)
 
 
 ## 0.11.4    2017-01-18
 
-* Compatibility with Ruby 2.4 [#59](https://github.com/lfittl/pg_query/pull/59) [@merqlove](https://github.com/merqlove)
-* Deparse varchar and numeric casts without arguments [#61](https://github.com/lfittl/pg_query/pull/61) [@jcsjcs](https://github.com/jcsjcs)
+* Compatibility with Ruby 2.4 [#59](https://github.com/pganalyze/pg_query/pull/59) [@merqlove](https://github.com/merqlove)
+* Deparse varchar and numeric casts without arguments [#61](https://github.com/pganalyze/pg_query/pull/61) [@jcsjcs](https://github.com/jcsjcs)
 
 
 ## 0.11.3    2016-12-06
@@ -118,11 +229,11 @@
   * Cut off fingerprints at 100 nodes deep to avoid excessive runtimes/memory
   * Fix warning on Linux due to missing asprintf include
 * Improved deparsing [@jcsjcs](https://github.com/jcsjcs)
-  * Float [#54](https://github.com/lfittl/pg_query/pull/54)
-  * BETWEEN [#55](https://github.com/lfittl/pg_query/pull/55)
-  * NULLIF [#56](https://github.com/lfittl/pg_query/pull/56)
-  * SELECT NULL and BooleanTest [#57](https://github.com/lfittl/pg_query/pull/57)
-* Fix build on BSD systems [#58](https://github.com/lfittl/pg_query/pull/58) [@myfreeweb](https://github.com/myfreeweb)
+  * Float [#54](https://github.com/pganalyze/pg_query/pull/54)
+  * BETWEEN [#55](https://github.com/pganalyze/pg_query/pull/55)
+  * NULLIF [#56](https://github.com/pganalyze/pg_query/pull/56)
+  * SELECT NULL and BooleanTest [#57](https://github.com/pganalyze/pg_query/pull/57)
+* Fix build on BSD systems [#58](https://github.com/pganalyze/pg_query/pull/58) [@myfreeweb](https://github.com/myfreeweb)
 
 
 ## 0.11.2    2016-06-27
@@ -141,9 +252,9 @@
 ## 0.11.0    2016-06-22
 
 * Improved table name analysis (#tables method)
-  * Don't include CTE names, make them accessible as #cte_names instead [#52](https://github.com/lfittl/pg_query/issues/52)
-  * Include table names in target list sub selects [#38](https://github.com/lfittl/pg_query/issues/38)
-  * Add support for ORDER/GROUP BY, HAVING, and booleans in WHERE [#53](https://github.com/lfittl/pg_query/pull/53) [@jcoleman](https://github.com/jcoleman)
+  * Don't include CTE names, make them accessible as #cte_names instead [#52](https://github.com/pganalyze/pg_query/issues/52)
+  * Include table names in target list sub selects [#38](https://github.com/pganalyze/pg_query/issues/38)
+  * Add support for ORDER/GROUP BY, HAVING, and booleans in WHERE [#53](https://github.com/pganalyze/pg_query/pull/53) [@jcoleman](https://github.com/jcoleman)
   * Fix parsing of DROP TYPE statements
 
 
@@ -152,19 +263,19 @@
 * Based on PostgreSQL 9.5.3
 * Use LLVM extracted parser for significantly improved build times (via libpg_query)
 * Deparsing Improvements
-  * SET statements [#48](https://github.com/lfittl/pg_query/pull/48) [@Winslett](https://github.com/Winslett)
-  * LIKE/NOT LIKE [#49](https://github.com/lfittl/pg_query/pull/49) [@Winslett](https://github.com/Winslett)
-  * CREATE FUNCTION improvements [#50](https://github.com/lfittl/pg_query/pull/50) [@Winslett](https://github.com/Winslett)
+  * SET statements [#48](https://github.com/pganalyze/pg_query/pull/48) [@Winslett](https://github.com/Winslett)
+  * LIKE/NOT LIKE [#49](https://github.com/pganalyze/pg_query/pull/49) [@Winslett](https://github.com/Winslett)
+  * CREATE FUNCTION improvements [#50](https://github.com/pganalyze/pg_query/pull/50) [@Winslett](https://github.com/Winslett)
 
 
 ## 0.9.2    2016-05-03
 
-* Fix issue with A_CONST string values in `.parsetree` compatibility layer (Fixes [#47](https://github.com/lfittl/pg_query/issues/47))
+* Fix issue with A_CONST string values in `.parsetree` compatibility layer (Fixes [#47](https://github.com/pganalyze/pg_query/issues/47))
 
 
 ## 0.9.1    2016-04-20
 
-* Add support for Ruby 1.9 (Fixes [#44](https://github.com/lfittl/pg_query/issues/44))
+* Add support for Ruby 1.9 (Fixes [#44](https://github.com/pganalyze/pg_query/issues/44))
 
 
 ## 0.9.0    2016-04-17
@@ -190,14 +301,14 @@
 ## 0.7.2    2015-12-20
 
 * Deparsing
-  * Quote all column refs [#40](https://github.com/lfittl/pg_query/pull/40) [@avinoamr](https://github.com/avinoamr)
-  * Quote all range vars [#43](https://github.com/lfittl/pg_query/pull/43) [@avinoamr](https://github.com/avinoamr)
-  * Support for COUNT(DISTINCT ...) [#42](https://github.com/lfittl/pg_query/pull/42) [@avinoamr](https://github.com/avinoamr)
+  * Quote all column refs [#40](https://github.com/pganalyze/pg_query/pull/40) [@avinoamr](https://github.com/avinoamr)
+  * Quote all range vars [#43](https://github.com/pganalyze/pg_query/pull/43) [@avinoamr](https://github.com/avinoamr)
+  * Support for COUNT(DISTINCT ...) [#42](https://github.com/pganalyze/pg_query/pull/42) [@avinoamr](https://github.com/avinoamr)
 
 
 ## 0.7.1    2015-11-17
 
-* Abstracted parser access into libpg_query [#24](https://github.com/lfittl/pg_query/pull/35)
+* Abstracted parser access into libpg_query [#24](https://github.com/pganalyze/pg_query/pull/35)
 * libpg_query
   * Use UTF-8 encoding for parsing [#4](https://github.com/lfittl/libpg_query/pull/4) [@zhm](https://github.com/zhm)
   * Add type to A_CONST nodes[#5](https://github.com/lfittl/libpg_query/pull/5) [@zhm](https://github.com/zhm)
@@ -205,20 +316,20 @@
 
 ## 0.7.0    2015-10-17
 
-* Restructure build process to use upstream tarballs [#35](https://github.com/lfittl/pg_query/pull/35)
-  * Avoid bison/flex dependency to make deployment easier [#31](https://github.com/lfittl/pg_query/issues/31)
-* Solve issues with deployments to Heroku [#32](https://github.com/lfittl/pg_query/issues/32)
+* Restructure build process to use upstream tarballs [#35](https://github.com/pganalyze/pg_query/pull/35)
+  * Avoid bison/flex dependency to make deployment easier [#31](https://github.com/pganalyze/pg_query/issues/31)
+* Solve issues with deployments to Heroku [#32](https://github.com/pganalyze/pg_query/issues/32)
 * Deparsing
-  * HAVING and FOR UPDATE [#36](https://github.com/lfittl/pg_query/pull/36) [@JackDanger](https://github.com/JackDanger)
+  * HAVING and FOR UPDATE [#36](https://github.com/pganalyze/pg_query/pull/36) [@JackDanger](https://github.com/JackDanger)
 
 
 ## 0.6.4    2015-10-01
 
 * Deparsing
-  * Constraints & Interval Types [#28](https://github.com/lfittl/pg_query/pull/28) [@JackDanger](https://github.com/JackDanger)
-  * Cross joins [#29](https://github.com/lfittl/pg_query/pull/29) [@mme](https://github.com/mme)
-  * ALTER TABLE [#30](https://github.com/lfittl/pg_query/pull/30) [@JackDanger](https://github.com/JackDanger)
-  * LIMIT and OFFSET [#33](https://github.com/lfittl/pg_query/pull/33) [@jcsjcs](https://github.com/jcsjcs)
+  * Constraints & Interval Types [#28](https://github.com/pganalyze/pg_query/pull/28) [@JackDanger](https://github.com/JackDanger)
+  * Cross joins [#29](https://github.com/pganalyze/pg_query/pull/29) [@mme](https://github.com/mme)
+  * ALTER TABLE [#30](https://github.com/pganalyze/pg_query/pull/30) [@JackDanger](https://github.com/JackDanger)
+  * LIMIT and OFFSET [#33](https://github.com/pganalyze/pg_query/pull/33) [@jcsjcs](https://github.com/jcsjcs)
 
 
 ## 0.6.3    2015-08-20

data/README.md

@@ -1,10 +1,10 @@
-# pg_query [ ![](https://img.shields.io/gem/v/pg_query.svg)](https://rubygems.org/gems/pg_query) [ ![](https://img.shields.io/gem/dt/pg_query.svg)](https://rubygems.org/gems/pg_query) [ ![](https://travis-ci.org/lfittl/pg_query.svg?branch=master)](https://travis-ci.org/lfittl/pg_query)
+# pg_query [ ![](https://img.shields.io/gem/v/pg_query.svg)](https://rubygems.org/gems/pg_query) [ ![](https://img.shields.io/gem/dt/pg_query.svg)](https://rubygems.org/gems/pg_query)
 
 This Ruby extension uses the actual PostgreSQL server source to parse SQL queries and return the internal PostgreSQL parsetree.
 
 In addition the extension allows you to normalize queries (replacing constant values with ?) and parse these normalized queries into a parsetree again.
 
-When you build this extension, it builds parts of the PostgreSQL server source (see [libpg_query](https://github.com/lfittl/libpg_query)), and then statically links it into this extension.
+When you build this extension, it builds parts of the PostgreSQL server source (see [libpg_query](https://github.com/pganalyze/libpg_query)), and then statically links it into this extension.
 
 This is slightly crazy, but is the only reliable way of parsing all valid PostgreSQL queries.
 
@@ -25,17 +25,49 @@ Due to compiling parts of PostgreSQL, installation might take a while on slower
 ```ruby
 PgQuery.parse("SELECT 1")
 
-=> #<PgQuery:0x007fe92b27ea18
- @tree=
-  [{"SelectStmt"=>
-     {"targetList"=>
-       [{"ResTarget"=>
-          {"val"=>{"A_Const"=>{"val"=>{"Integer"=>{"ival"=>1}}, "location"=>7}},
-           "location"=>7}}],
-      "op"=>0,
-  }}],
- @query="SELECT 1",
- @warnings=[]>
+=> #<PgQuery::ParserResult:0x00007fb69a958820
+  @query="SELECT 1",
+  @tree=<PgQuery::ParseResult:
+    version: 130002,
+    stmts: [
+      <PgQuery::RawStmt:
+        stmt: <PgQuery::Node:
+          select_stmt: <PgQuery::SelectStmt:
+            distinct_clause: [],
+            target_list: [
+              <PgQuery::Node:
+                res_target: <PgQuery::ResTarget:
+                  name: "",
+                  indirection: [],
+                  val: <PgQuery::Node:
+                    a_const: <PgQuery::A_Const:
+                      val: <PgQuery::Node:
+                        integer: <PgQuery::Integer: ival: 1>
+                      >,
+                      location: 7
+                    >
+                  >,
+                  location: 7
+                >
+              >
+            ],
+            from_clause: [],
+            group_clause: [],
+            window_clause: [],
+            values_lists: [],
+            sort_clause: [],
+            limit_option: :LIMIT_OPTION_DEFAULT,
+            locking_clause: [],
+            op: :SETOP_NONE,
+            all: false
+          >
+        >,
+        stmt_location: 0,
+        stmt_len: 0
+      >
+    ]
+  >,
+  @warnings=[]>
 ```
 
 ### Modifying a parsed query and turning it into SQL again
@@ -43,35 +75,14 @@ PgQuery.parse("SELECT 1")
 ```ruby
 parsed_query = PgQuery.parse("SELECT * FROM users")
 
-=> #<PgQuery:0x007ff3e956c8b0
- @tree=
-  [{"SelectStmt"=>
-    {"targetList"=>
-      [{"ResTarget"=>
-        {"val"=>
-          {"ColumnRef"=> {"fields"=>[{"A_Star"=>{}}], "location"=>7}},
-         "location"=>7}
-      }],
-     "fromClause"=>
-      [{"RangeVar"=>
-        {"relname"=>"users",
-         "inhOpt"=>2,
-         "relpersistence"=>"p",
-         "location"=>14}}],
-   }}],
- @query="SELECT * FROM users",
- @warnings=[]>
-
 # Modify the parse tree in some way
-parsed_query.tree[0]['SelectStmt']['fromClause'][0]['RangeVar']['relname'] = 'other_users'
+parsed_query.tree.stmts[0].stmt.select_stmt.from_clause[0].range_var.relname = 'other_users'
 
 # Turn it into SQL again
 parsed_query.deparse
-=> "SELECT * FROM \"other_users\""
+=> "SELECT * FROM other_users"
 ```
 
-Note: The deparsing feature is experimental and does not support outputting all SQL yet.
-
 ### Parsing a normalized query
 
 ```ruby
@@ -83,29 +94,10 @@ PgQuery.normalize("SELECT 1 FROM x WHERE y = 'foo'")
 # Parsing a normalized query (pre-Postgres 10 style)
 PgQuery.parse("SELECT ? FROM x WHERE y = ?")
 
-=> #<PgQuery:0x007fb99455a438
- @tree=
-  [{"SelectStmt"=>
-     {"targetList"=>
-       [{"ResTarget"=>
-          {"val"=>{"ParamRef"=>{"location"=>7}},
-           "location"=>7}}],
-      "fromClause"=>
-       [{"RangeVar"=>
-          {"relname"=>"x",
-           "inhOpt"=>2,
-           "relpersistence"=>"p",
-           "location"=>14}}],
-      "whereClause"=>
-       {"A_Expr"=>
-         {"kind"=>0,
-          "name"=>[{"String"=>{"str"=>"="}}],
-          "lexpr"=>{"ColumnRef"=>{"fields"=>[{"String"=>{"str"=>"y"}}], "location"=>22}},
-          "rexpr"=>{"ParamRef"=>{"location"=>26}},
-          "location"=>24}},
-  }}],
- @query="SELECT ? FROM x WHERE y = ?",
- @warnings=[]>
+=> #<PgQuery::ParserResult:0x00007fb69a97a5d8
+  @query="SELECT ? FROM x WHERE y = ?",
+  @tree=<PgQuery::ParseResult: ...>,
+  @warnings=[]>
 ```
 
 ### Extracting tables from a query
@@ -129,21 +121,21 @@ PgQuery.parse("SELECT ? FROM x WHERE x.y = ? AND z = ?").filter_columns
 ```ruby
 PgQuery.parse("SELECT 1").fingerprint
 
-=> "8e1acac181c6d28f4a923392cf1c4eda49ee4cd2"
+=> "50fde20626009aba"
 
 PgQuery.parse("SELECT 2; --- comment").fingerprint
 
-=> "8e1acac181c6d28f4a923392cf1c4eda49ee4cd2"
+=> "50fde20626009aba"
 
-# Faster fingerprint method that is implemented inside the native library
+# Faster fingerprint method that is implemented inside the native C library
 PgQuery.fingerprint("SELECT ?")
 
-=> "8e1acac181c6d28f4a923392cf1c4eda49ee4cd2"
+=> "50fde20626009aba"
 ```
 
 ## Differences from Upstream PostgreSQL
 
-This gem is based on [libpg_query](https://github.com/lfittl/libpg_query),
+This gem is based on [libpg_query](https://github.com/pganalyze/libpg_query),
 which uses the latest stable PostgreSQL version, but with a patch applied
 to support parsing normalized queries containing `?` replacement characters.
 
@@ -151,15 +143,34 @@ to support parsing normalized queries containing `?` replacement characters.
 
 Currently tested and officially supported Ruby versions:
 
-* MRI 2.1
-* MRI 2.2
-* MRI 2.3
-* MRI 2.4
+* CRuby 2.5
+* CRuby 2.6
+* CRuby 2.7
+* CRuby 3.0
+
+Not supported:
+
+* JRuby: `pg_query` relies on a C extension, which is discouraged / not properly supported for JRuby
+* TruffleRuby: GraalVM [does not support sigjmp](https://www.graalvm.org/reference-manual/llvm/NativeExecution/), which is used by the Postgres error handling code (`pg_query` uses a copy of the Postgres parser & error handling code)
+
+## Developer tasks
+
+### Update libpg_query source
+
+In order to update to a newer Postgres parser, first update [libpg_query](https://github.com/pganalyze/libpg_query) to the new Postgres version and tag a release.
+
+Once that is done, follow the following steps:
+
+1. Update `LIB_PG_QUERY_TAG` and `LIB_PG_QUERY_SHA256SUM` in `Rakefile`
+
+2. Run `rake update_source` to update the source code
+
+3. Commit the `Rakefile` and the modified files in `ext/pg_query` to this source tree and make a PR
 
 
 ## Resources
 
-See [libpg_query](https://github.com/lfittl/libpg_query/blob/10-latest/README.md#resources) for pg_query in other languages, as well as products/tools built on pg_query.
+See [libpg_query](https://github.com/pganalyze/libpg_query/blob/13-latest/README.md#resources) for pg_query in other languages, as well as products/tools built on pg_query.
 
 ## Original Author