|
66 | 66 | </sect2>
|
67 | 67 | <sect2>
|
68 | 68 | <title>Changes</title>
|
| 69 | + |
| 70 | + <sect3> |
| 71 | + <title>Replication and Recovery</title> |
| 72 | + <itemizedlist> |
| 73 | + |
| 74 | + <listitem> |
| 75 | + <para> |
| 76 | + <emphasis>Support named restore points</emphasis> |
| 77 | + </para> |
| 78 | + <para> |
| 79 | + Named restore points can be created using a new server function, |
| 80 | + pg_create_restore_point. A new recovery.conf parameter, |
| 81 | + recovery_target_name, allows recovery to stop at a named restore |
| 82 | + point. |
| 83 | + </para> |
| 84 | + </listitem> |
| 85 | + |
| 86 | + <listitem> |
| 87 | + <para> |
| 88 | + <emphasis>Add new recovery.conf parameter, pause_at_recovery_target, |
| 89 | + which defaults to on</emphasis> |
| 90 | + </para> |
| 91 | + <para> |
| 92 | + This is a behavior change from previous releases, which entered normal |
| 93 | + running upon reaching the recovery target. |
| 94 | + </para> |
| 95 | + </listitem> |
| 96 | + |
| 97 | + <listitem> |
| 98 | + <para> |
| 99 | + <emphasis>Add pg_is_xlog_replay_paused, pg_xlog_replay_pause, and |
| 100 | + pg_xlog_replay_resume functions</emphasis> |
| 101 | + </para> |
| 102 | + </listitem> |
| 103 | + |
| 104 | + <listitem> |
| 105 | + <para> |
| 106 | + <emphasis>Allow standby servers to send information on running |
| 107 | + transactions back to the master</emphasis> |
| 108 | + </para> |
| 109 | + <para> |
| 110 | + When enabled, this prevents most recovery conflicts on the slave, |
| 111 | + but may cause MVCC bloat on the master. |
| 112 | + </para> |
| 113 | + </listitem> |
| 114 | + |
| 115 | + <listitem> |
| 116 | + <para> |
| 117 | + <emphasis>Support streaming base backups</emphasis> |
| 118 | + </para> |
| 119 | + <para> |
| 120 | + A new client, pg_basebackup, can be used to perform a streaming base |
| 121 | + backup. |
| 122 | + </para> |
| 123 | + </listitem> |
| 124 | + |
| 125 | + </itemizedlist> |
| 126 | + </sect3> |
| 127 | + |
69 | 128 | <sect3>
|
70 | 129 | <title>SQL Features</title>
|
71 | 130 | <itemizedlist>
|
|
479 | 538 | </para>
|
480 | 539 | </listitem>
|
481 | 540 |
|
482 |
| - <listitem> |
483 |
| - <para> |
484 |
| - <emphasis>Add new recovery.conf parameter, pause_at_recovery_target, |
485 |
| - which defaults to on.</emphasis> |
486 |
| - </para> |
487 |
| - <para> |
488 |
| - This is a behavior change from previous releases, which entered normal |
489 |
| - running upon reaching the recovery target. |
490 |
| - </para> |
491 |
| - </listitem> |
492 |
| - |
493 |
| - <listitem> |
494 |
| - <para> |
495 |
| - <emphasis>Add new recovery.conf parameter, recovery_target_name, |
496 |
| - allowing recovery to proceed to a named restore point</emphasis> |
497 |
| - </para> |
498 |
| - <para> |
499 |
| - Named restore points can be created using a new server function, |
500 |
| - pg_create_restore_point. |
501 |
| - </para> |
502 |
| - </listitem> |
503 |
| - |
504 | 541 | </itemizedlist>
|
505 | 542 | </sect3>
|
506 | 543 | <sect3>
|
|
626 | 663 | </para>
|
627 | 664 | </listitem>
|
628 | 665 |
|
629 |
| - <listitem> |
630 |
| - <para> |
631 |
| - <emphasis>Allow standby servers to send information on running |
632 |
| - transactions back to the master</emphasis> |
633 |
| - </para> |
634 |
| - <para> |
635 |
| - When enabled, this prevents most recovery conflicts on the slave, |
636 |
| - but may cause MVCC bloat on the master. |
637 |
| - </para> |
638 |
| - </listitem> |
639 |
| - |
640 | 666 | </itemizedlist>
|
641 | 667 | </sect3>
|
642 | 668 | <sect3>
|
|
752 | 778 | </para>
|
753 | 779 | </listitem>
|
754 | 780 |
|
755 |
| - <listitem> |
756 |
| - <para> |
757 |
| - <emphasis>Add pg_is_xlog_replay_paused, pg_xlog_replay_pause, and |
758 |
| - pg_xlog_replay_resume functions.</emphasis> |
759 |
| - </para> |
760 |
| - </listitem> |
761 |
| - |
762 | 781 | <listitem>
|
763 | 782 | <para>
|
764 | 783 | <emphasis>Change pg_last_xlog_receive_location not to move
|
|
805 | 824 | </para>
|
806 | 825 | </listitem>
|
807 | 826 |
|
808 |
| - <listitem> |
809 |
| - <para> |
810 |
| - <emphasis>Support streaming base backups.</emphasis> |
811 |
| - </para> |
812 |
| - <para> |
813 |
| - A new client, pg_basebackup, can be used to perform a streaming base |
814 |
| - backup. |
815 |
| - </para> |
816 |
| - </listitem> |
817 |
| - |
818 | 827 | <listitem>
|
819 | 828 | <para>
|
820 | 829 | <emphasis>Add a directory output format to pg_dump</emphasis>
|
|
0 commit comments