|
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-1-1"> |
| 4 | + <title>Postgres Pro 9.6.1.1</title> |
| 5 | + <note> |
| 6 | + <title>Release Date</title> |
| 7 | + <simpara>2016-11-01</simpara> |
| 8 | + </note> |
| 9 | + <sect2> |
| 10 | + <title>Overview</title> |
| 11 | + <para>This release is based on <productname>PostgreSQL</productname> |
| 12 | + 9.6.1</para> |
| 13 | + <para>Major enhancements over <productname>Postgres Pro</productname> |
| 14 | + 9.6.0.1 include:</para> |
| 15 | + <para>Added fix for <application>pg_buffercache</application> module, |
| 16 | + which improves response database in the case of connected |
| 17 | + monitoring tools.</para> |
| 18 | + <para>Added new <application>pgpro_edition()</application> function, |
| 19 | + which returns a name of <productname>Postgres Pro</productname> edition, |
| 20 | + i.e. <literal>standard</literal> or <literal>enterprise</literal>. |
| 21 | + </para> |
| 22 | + </sect2> |
| 23 | + <sect2> |
| 24 | + <title>Migration to Version 9.6.1.1</title> |
| 25 | + <para>A dump/restore using <xref linkend="app-pg-dumpall">, or |
| 26 | + use of <xref linkend="pgupgrade">, is required for those |
| 27 | + wishing to migrate data from any previous major release. |
| 28 | + </para> |
| 29 | + <para>A dump/restore is not required for those running 9.6.0.1.</para> |
| 30 | + <para>However, if you are upgrading from vanilla PostgreSQL 9.6.x, some |
| 31 | + catalog changes should be applied. |
| 32 | + </para> |
| 33 | + <para>If you use binary packages, and your database is in the default |
| 34 | + location, this upgrade should be performed automatically. If you've |
| 35 | + compiled Postgres Pro from source or create your database in |
| 36 | + non-default location, running <literal>initdb</literal> manually, you |
| 37 | + should run <literal>pgpro_upgrade</literal> script provided in this |
| 38 | + distribution. |
| 39 | + </para> |
| 40 | + <para>Before running script, you should stop postgres service. Script |
| 41 | + should be run as user, owning the database (typically postgres) and |
| 42 | + PGDATA environment variable should be set to the directory where |
| 43 | + database resides. |
| 44 | + </para> |
| 45 | + </sect2> |
| 46 | +</sect1> |
3 | 47 | <sect1 id="release-pro-9-6-0-1">
|
4 | 48 | <title>Postgres Pro 9.6.0.1</title>
|
5 | 49 | <note>
|
|
0 commit comments