|
1 | 1 | <!-- doc/src/sgml/release-pro-9.6.sgml --> |
2 | 2 | <!-- See header comment in release.sgml about typical markup --> |
| 3 | +<sect1 id="release-pro-9-6-3-2"> |
| 4 | + <title>Postgres Pro 9.6.3.2</title> |
| 5 | + <note> |
| 6 | + <title>Release Date</title> |
| 7 | + <simpara>2017-07-12</simpara> |
| 8 | + </note> |
| 9 | + <sect2> |
| 10 | + <title>Overview</title> |
| 11 | + <para>This release is based on <productname>Postgres Pro</productname> |
| 12 | + <link linkend="release-pro-9-6-3-1">9.6.3.1</link> and |
| 13 | + <productname>PostgreSQL</productname> <link linkend="release-9-6-3">9.6.3</link>.</para> |
| 14 | + <para>Major enhancements over <productname>Postgres Pro</productname> |
| 15 | + 9.6.3.1 include:</para> |
| 16 | + <itemizedlist> |
| 17 | + <listitem> |
| 18 | + <para>Updated the <link linkend="app-pgprobackup"><application>pg_probackup</application></link> backup manager to version 2.0 that includes the following new features:</para> |
| 19 | + <itemizedlist> |
| 20 | + <listitem> |
| 21 | + <para> |
| 22 | + Saving backups for different databases in a single backup catalog |
| 23 | + </para> |
| 24 | + <para> |
| 25 | + Storing backup data in a compressed state to save disk space |
| 26 | + </para> |
| 27 | + <para> |
| 28 | + Extended logging settings |
| 29 | + </para> |
| 30 | + </listitem> |
| 31 | + </itemizedlist> |
| 32 | + </listitem> |
| 33 | + <listitem> |
| 34 | + <para>Added distribution for Debian 9.</para> |
| 35 | + </listitem> |
| 36 | + <listitem> |
| 37 | + <para>Added upstream patches that fix potential data corruption during freeze.</para> |
| 38 | + </listitem> |
| 39 | + </itemizedlist> |
| 40 | + </sect2> |
| 41 | + <sect2> |
| 42 | + <title>Migration to Version 9.6.3.2</title> |
| 43 | + <para>A dump/restore using <xref linkend="app-pg-dumpall">, or |
| 44 | + use of <xref linkend="pgupgrade">, is required for those |
| 45 | + wishing to migrate data from any previous major release. |
| 46 | + </para> |
| 47 | + <para>A dump/restore is not required for those running 9.6.3.1.</para> |
| 48 | + <para>However, if you are upgrading from vanilla PostgreSQL 9.6.x, some |
| 49 | + catalog changes should be applied. |
| 50 | + </para> |
| 51 | + <para>If you use binary packages, and your database is in the default |
| 52 | + location, this upgrade should be performed automatically. If you've |
| 53 | + compiled Postgres Pro from source or create your database in a |
| 54 | + non-default location, running <literal>initdb</literal> manually, you |
| 55 | + should run <literal>pgpro_upgrade</literal> script provided in this |
| 56 | + distribution. |
| 57 | + </para> |
| 58 | + <para>Before running the script, you should stop postgres service. |
| 59 | + Script should be run on behalf of the user owning the database |
| 60 | + (typically postgres) and PGDATA environment variable should be |
| 61 | + set to the directory where database resides. |
| 62 | + </para> |
| 63 | + </sect2> |
| 64 | +</sect1> |
3 | 65 | <sect1 id="release-pro-9-6-3-1"> |
4 | 66 | <title>Postgres Pro 9.6.3.1</title> |
5 | 67 | <note> |
|