|
1 | 1 | <!-- doc/src/sgml/release-proee-9.6.sgml -->
|
| 2 | +<sect1 id="release-proee-9-6-4-1"> |
| 3 | + <title>&productname; 9.6.4.1</title> |
| 4 | + <note> |
| 5 | + <title>Release Date</title> |
| 6 | + <simpara>2017-08-16</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-3-2">9.6.3.2</link> and |
| 12 | + <productname>Postgres Pro Standard</productname> <link linkend="release-pro-9-6-4-1">9.6.4.1</link>.</para> |
| 13 | + <para>Major enhancements over <productname>Postgres Pro Enterprise</productname> |
| 14 | + 9.6.3.2 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 2.0</para> |
| 20 | + </listitem> |
| 21 | + <listitem> |
| 22 | + <para>Module <link linkend="pg-pathman"><application>pg_pathman</application></link> updated to version 1.4.2</para> |
| 23 | + </listitem> |
| 24 | + <listitem> |
| 25 | + <para> |
| 26 | + In Compressed File System (CFS), fixed a memory leak. |
| 27 | + </para> |
| 28 | + </listitem> |
| 29 | + <listitem> |
| 30 | + <para> |
| 31 | + Fixed potential data corruption in the online_analyze contrib module. |
| 32 | + </para> |
| 33 | + </listitem> |
| 34 | + <listitem> |
| 35 | + <para>Improved <application>multimaster</application> extension:</para> |
| 36 | + <itemizedlist> |
| 37 | + <listitem> |
| 38 | + <para> |
| 39 | + Fixed <command>ALTER SYSTEM SET</command> |
| 40 | + command. <!-- PGPRO-841 --> |
| 41 | + </para> |
| 42 | + </listitem> |
| 43 | + <listitem> |
| 44 | + <para> |
| 45 | + Fixed unexpected timeout of asynchronous connection. <!-- PGPRO-682 --> |
| 46 | + </para> |
| 47 | + </listitem> |
| 48 | + <listitem> |
| 49 | + <para> |
| 50 | + Fixed invalid transaction state while <application>walsender</application> executing |
| 51 | + snapshot. <!-- PGPRO-682 --> |
| 52 | + </para> |
| 53 | + </listitem> |
| 54 | + </itemizedlist> |
| 55 | + </listitem> |
| 56 | + <listitem> |
| 57 | + <para>Added primary key to schedule tables for the support of <application>multimaster</application> in |
| 58 | + <application>pgpro_scheduler</application>. <!-- PGPRO-837 --> |
| 59 | + </para> |
| 60 | + </listitem> |
| 61 | + |
| 62 | + <!-- PGPRO-813 (pgpro_upgrade fixes) Std(9.6.4.1) EE (9.6.4.1) --> |
| 63 | + |
| 64 | + </itemizedlist> |
| 65 | + </sect2> |
| 66 | + <sect2> |
| 67 | + <title>Migration to Version &productname; 9.6.4.1</title> |
| 68 | + |
| 69 | + <para>A dump/restore using <xref linkend="app-pg-dumpall">, or |
| 70 | + use of <xref linkend="pgupgrade">, is required for those |
| 71 | + wishing to migrate data from any previous major release.</para> |
| 72 | + |
| 73 | + <para>Dump/restore is necessary when migrating from <productname>PostgreSQL</productname>, |
| 74 | + <productname>Postgres Pro Standard</productname>, or <productname>Postgres Pro Enterprise</productname> edition.</para> |
| 75 | + |
| 76 | + <para>For upgrades from previous releases of <productname>Postgres Pro Enterprise</productname>, <productname>Postgres Pro Standard</productname>, or |
| 77 | + PostgreSQL 9.6.x, some catalog changes should be applied.</para> |
| 78 | + |
| 79 | + <para>If you use binary packages, and your database is in the default |
| 80 | + location, this upgrade should be performed automatically. If you've |
| 81 | + created your database in |
| 82 | + a non-default location, running <literal>initdb</literal> manually, you |
| 83 | + should run the <literal>pgpro_upgrade</literal> script provided in this |
| 84 | + distribution. |
| 85 | + </para> |
| 86 | + |
| 87 | + <para>Before running the script, you should stop the <literal>postgres</literal> service. |
| 88 | + The script should be run on behalf of the user owning the database |
| 89 | + (typically <literal>postgres</literal>), and the <envar>PGDATA</envar> environment variable should be |
| 90 | + set to the directory where the database resides. |
| 91 | + </para> |
| 92 | + </sect2> |
| 93 | +</sect1> |
2 | 94 | <sect1 id="release-proee-9-6-3-2">
|
3 | 95 | <title>&productname; 9.6.3.2</title>
|
4 | 96 | <note>
|
5 | 97 | <title>Release Date</title>
|
6 |
| - <simpara>2017-05-28</simpara> |
| 98 | + <simpara>2017-06-28</simpara> |
7 | 99 | </note>
|
8 | 100 | <sect2>
|
9 | 101 | <title>Overview</title>
|
|
0 commit comments