|
1 | 1 | <!-- doc/src/sgml/release-proee-9.6.sgml -->
|
| 2 | +<sect1 id="release-proee-9-6-3-1"> |
| 3 | + <title>&productname; 9.6.3.1</title> |
| 4 | + <note> |
| 5 | + <title>Release Date</title> |
| 6 | + <simpara>2017-05-25</simpara> |
| 7 | + </note> |
| 8 | + <sect2> |
| 9 | + <title>Overview</title> |
| 10 | + <para>This release is based on <productname>Postgres Pro Enterprise</productname> |
| 11 | + <link linkend="release-proee-9-6-2-1">9.6.2.1</link> and |
| 12 | + <productname>Postgres Pro Standard</productname> <link linkend="release-pro-9-6-3-1">9.6.3.1</link>.</para> |
| 13 | + <para>Major enhancements over <productname>Postgres Pro Enterprise</productname> |
| 14 | + 9.6.2.1 include:</para> |
| 15 | + <itemizedlist> |
| 16 | + <listitem> |
| 17 | + <para>Updated |
| 18 | + the <link linkend="app-pgprobackup"><application>pg_probackup</application></link> |
| 19 | + backup manager to version 1.1.11. Command-line interface |
| 20 | + has been changed.</para> |
| 21 | + </listitem> |
| 22 | + <listitem><para>Improved <application>multimaster</application> |
| 23 | + extension: |
| 24 | + <itemizedlist> |
| 25 | + <listitem> |
| 26 | + <para>Added support for savepoints. |
| 27 | + </para> |
| 28 | + </listitem> |
| 29 | + <listitem> |
| 30 | + <para>Extended support for <acronym>DDL</acronym> statements. |
| 31 | + </para> |
| 32 | + </listitem> |
| 33 | + </itemizedlist> |
| 34 | + </para> |
| 35 | + <para>(See <xref linkend="multimaster">.)</para> |
| 36 | + </listitem> |
| 37 | + <listitem><para>Enabled support for multiple data types in RUM index, |
| 38 | + such as <literal>int</literal>, <literal>bigint</literal>, |
| 39 | + <literal>float</literal>, <literal>time</literal>, <literal>interval</literal>, |
| 40 | + <literal>bytea</literal>, <literal>text</literal>, |
| 41 | + and more. You can now store <literal>tsvector</literal> type together |
| 42 | + with other types in a single index. |
| 43 | + </para><para>(See <xref linkend="rum">.)</para> |
| 44 | + </listitem> |
| 45 | + <listitem><para>Improved autonomous transaction support: |
| 46 | + <itemizedlist> |
| 47 | + <listitem> |
| 48 | + <para>Fixed handling of multixact IDs. |
| 49 | + </para> |
| 50 | + </listitem> |
| 51 | + <listitem> |
| 52 | + <para>Speeded up execution of autonomous transactions. |
| 53 | + </para> |
| 54 | + </listitem> |
| 55 | + </itemizedlist> |
| 56 | + </para><para>(See <xref linkend="atx">.)</para> |
| 57 | + </listitem> |
| 58 | + </itemizedlist> |
| 59 | + </sect2> |
| 60 | + <sect2> |
| 61 | + <title>Migration to Version &productname; 9.6.3.1</title> |
| 62 | + |
| 63 | + <para>A dump/restore using <xref linkend="app-pg-dumpall">, or |
| 64 | + use of <xref linkend="pgupgrade">, is required for those |
| 65 | + wishing to migrate data from any previous major release.</para> |
| 66 | + |
| 67 | + <para>Dump/restore is necessary when migrating from <productname>PostgreSQL</productname>, |
| 68 | + <productname>Postgres Pro Standard</productname>, or <productname>Postgres Pro Enterprise</productname> edition.</para> |
| 69 | + |
| 70 | + <para>For upgrades from previous releases of <productname>Postgres Pro Enterprise</productname>, <productname>Postgres Pro Standard</productname>, or |
| 71 | + PostgreSQL 9.6.x, some catalog changes should be applied.</para> |
| 72 | + |
| 73 | + <para>If you use binary packages, and your database is in the default |
| 74 | + location, this upgrade should be performed automatically. If you've |
| 75 | + created your database in |
| 76 | + a non-default location, running <literal>initdb</literal> manually, you |
| 77 | + should run the <literal>pgpro_upgrade</literal> script provided in this |
| 78 | + distribution. |
| 79 | + </para> |
| 80 | + |
| 81 | + <para>Before running the script, you should stop the <literal>postgres</literal> service. |
| 82 | + The script should be run on behalf of the user owning the database |
| 83 | + (typically <literal>postgres</literal>), and the <envar>PGDATA</envar> environment variable should be |
| 84 | + set to the directory where the database resides. |
| 85 | + </para> |
| 86 | + </sect2> |
| 87 | +</sect1> |
2 | 88 | <sect1 id="release-proee-9-6-2-1">
|
3 | 89 | <title>&productname; 9.6.2.1</title>
|
4 | 90 | <note>
|
|
115 | 201 |
|
116 | 202 | <para>If you use binary packages, and your database is in the default
|
117 | 203 | location, this upgrade should be performed automatically. If you've
|
118 |
| - compiled <productname>Postgres Pro Enterprise</productname> from source or created your database in |
| 204 | + created your database in |
119 | 205 | a non-default location, running <literal>initdb</literal> manually, you
|
120 | 206 | should run the <literal>pgpro_upgrade</literal> script provided in this
|
121 | 207 | distribution.
|
|
0 commit comments