* Fixes for `pg_replication_slot_advance` including returning `NULL` if slot is not advanced and changes for how the slot is updated depending on if it is a physical or logical replication slot
* Ensure `pg_resetwal` works with relative paths to data directory
* Fixes for query parallelism, including preventing a crash by ignoring "parallel append" for parallel unsafe paths in a query plan
-* `pg_upgrade` now uses the "fast ALTER TABLE .. ADD COLUMN" feature with a non-NULL default
+* Fix for `pg_upgrade` that ensures defaults are written when using the "fast ALTER TABLE .. ADD COLUMN" feature with a non-NULL default
* Add new configure flags introduced in PostgreSQL 11 to the corresponding Windows configure file
* Fix issue where `COPY FROM .. WITH HEADER` would drop a line after every 4,294,967,296 lines processed
* Ensure the "B" (bytes) parameter is accepted by all memory-related configuration parameters
* Several fixes for the JSONB transform in PL/Python and PL/Perl
* Several additional memory leak fixes
* Fix for potential replica server crashes where a replica would attempt to read a recycled WAL segment
-* Several fixes for XML support, including using the document node as the context for XMLTABLE Xpath queries as defined in the SQL standard
+* Several fixes for XML support, including using the document node as the context for XPath queries as defined in the SQL standard, which affects the `xpath` and `xpath_exists` functions
* Fix returning accurate results with "variance" and similar aggregate functions when executed using parallel query
This update also contains tzdata release 2018e, with updates for North Korea. The 2018e also reintroduces the negative-DST changes that were originally introduced in 2018a, which affects historical and present timestamps for Ireland (1971-), as well as historical timestamps for Namibia (1994-2017) and the former Czechoslovakia (1946-1947). If your application is storing timestamps with those timezones in the affected date ranges, we ask that you please test to ensure your applications behave as expected.
Testing for Bugs & Compatibility
--------------------------------
-The stability of each PostgreSQL release greatly depends on your, the community, to test the upcoming version with your workloads and testing tools in order to find bugs and regressions before the release of PostgreSQL 11. As this is a Beta, minor changes to database behaviors, feature details, and APIs are still possible. Your feedback and testing will help determine the final tweaks on the new features, so please test in the near future. The quality of user testing helps determine when we can make a final release.
+The stability of each PostgreSQL release greatly depends on you, the community, to test the upcoming version with your workloads and testing tools in order to find bugs and regressions before the release of PostgreSQL 11. As this is a Beta, minor changes to database behaviors, feature details, and APIs are still possible. Your feedback and testing will help determine the final tweaks on the new features, so please test in the near future. The quality of user testing helps determine when we can make a final release.
A list of [open issues](https://wiki.postgresql.org/wiki/PostgreSQL_11_Open_Items) is publicly available in the PostgreSQL wiki. You can [report bugs](https://www.postgresql.org/account/submitbug/) using this form on the PostgreSQL website: