postgrespro.git / summary / log / commit / refs

commit    1f7fc7670c7e0051b47bb4a4d6b41ff9e8af53fa
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Sat Sep 22 00:28:55 2018 +0000

    doc:  JIT is enabled by default in PG 12
    
    JIT was disabled by default in a PG 11 in a separate commit that will
    normally not appear in the PG 12 git logs.  Therefore, create a PG 12
    document and mention the fact that JIT is enabled by default in this
    release.  (A similar change in parallelism was missed in a prior
    release.)
    
    Reported-by: Andres Freund
    
    Discussion: https://postgr.es/m/20180922000554.qukbhhlagpnopvko@alap3.anarazel.de
    
    Backpatch-through: head


 doc/src/sgml/filelist.sgml   |  1 +
 doc/src/sgml/release-12.sgml | 11 +++++++++++
 doc/src/sgml/release.sgml    |  1 +
 3 files changed, 13 insertions(+)

diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index f010cd4c3b..48ac14a838 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -166,6 +166,7 @@
 <!ENTITY sourcerepo SYSTEM "sourcerepo.sgml">
 
 <!ENTITY release    SYSTEM "release.sgml">
+<!ENTITY release-12     SYSTEM "release-12.sgml">
 <!ENTITY release-11     SYSTEM "release-11.sgml">
 <!ENTITY release-10     SYSTEM "release-10.sgml">
 <!ENTITY release-9.6    SYSTEM "release-9.6.sgml">
diff --git a/doc/src/sgml/release-12.sgml b/doc/src/sgml/release-12.sgml
new file mode 100644
index 0000000000..b06fef287d
--- /dev/null
+++ b/doc/src/sgml/release-12.sgml
@@ -0,0 +1,11 @@
+<!-- doc/src/sgml/release-12.sgml -->
+<!-- See header comment in release.sgml about typical markup -->
+
+ <sect1 id="release-12">
+  <title>Release 12</title>
+
+  <para>JIT is enabled by default in this release.  It was disabled by
+  default in PG 11, so we document is enablement here.
+  </para>
+
+ </sect1>
diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index b78a942bcd..c4e763a043 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -76,6 +76,7 @@ For new features, add links to the documentation sections.
   The reason for splitting the release notes this way is so that appropriate
   subsets can easily be copied into back branches.
 -->
+&release-12;
 &release-11;
 &release-10;
 &release-9.6;


[parent: f77de4b0c0ad]