Re: PG 12 draft release notes
Ian Barwick <ian.barwick@2ndquadrant.com>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
doc: PG 12 relnotes: update wording on truncate/vacuum item
- 4f41a7227511 12.0 landed
-
docs: PG 12 relnotes, update btree items
- 4bfb79ff6b1f 12.0 landed
-
doc: PG 12 relnotes, list added snowball/FTS languages
- 968072837173 12.0 landed
-
doc: PG 12 relnotes, merge new SQL partition function items
- 6a631a454664 12.0 landed
-
docs: PG 12 release notes, support functions
- 728840fe13ac 12.0 landed
-
docs: PG 12 relnote adjustments based on feedback from Tom Lane
- 8e719d33fd25 12.0 landed
-
docs: adjust RECORD PG 12 relnote item
- 3468a04a3e49 12.0 landed
-
doc: adjust PG 12 relnotes item on float digit adjustment
- b84a801d6a67 12.0 landed
-
doc: adjustments for PG 12 release notes
- 32fe2e3194c7 12.0 landed
-
docs: fix duplicate wording in PG 12 release notes
- 34d40becfa7a 12.0 landed
-
doc: properly attibute PG 12 pgbench release note item
- 5d971565a799 12.0 landed
-
doc: PG 12 release notes: normalize attribution names
- f86b0c3c4653 12.0 landed
-
Refactor the fsync queue for wider use.
- 3eb77eba5a51 12.0 cited
-
Add "split after new tuple" nbtree optimization.
- f21668f328c8 12.0 cited
-
Add nbtree high key "continuescan" optimization.
- 29b64d1de7c7 12.0 cited
-
Allow amcheck to re-find tuples using new search.
- c1afd175b5b2 12.0 cited
-
Consider secondary factors during nbtree splits.
- fab250243387 12.0 cited
-
Partial implementation of SQL/JSON path language
- 72b6460336e8 12.0 cited
-
Allow extensions to generate lossy index conditions.
- 74dfe58a5927 12.0 cited
-
Make TupleTableSlots extensible, finish split of existing slot type.
- 4da597edf1ba 12.0 cited
-
Reduce path length for locking leaf B-tree pages during insertion
- d2086b08b023 12.0 cited
On 5/12/19 5:33 AM, Bruce Momjian wrote:
> I have posted a draft copy of the PG 12 release notes here:
>
> http://momjian.us/pgsql_docs/release-12.html
>
> They are committed to git. It includes links to the main docs, where
> appropriate. Our official developer docs will rebuild in a few hours.
In section "Authentication":
https://www.postgresql.org/docs/devel/release-12.html#id-1.11.6.5.5.3.7
the last two items are performance improvements not related to authentication;
presumably the VACUUM item would be better off in the "Utility Commands"
section and the TRUNCATE item in "General Performance"?
In section "Source code":
https://www.postgresql.org/docs/devel/release-12.html#id-1.11.6.5.5.12
the item "Add CREATE ACCESS METHOD command" doesn't seem related to the
source code itself, though I'm not sure where it should go.
Regards
Ian Barwick
--
Ian Barwick https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services