← Back to branch summary

~ubuntu-branches/ubuntu/oneiric/postgresql-9.1/oneiric-security

« back to all changes in this revision

Viewing changes to doc/src/sgml/html/warm-standby.html

  • Committer: Package Import Robot
  • Author(s): Martin Pitt
  • Date: 2013-02-05 18:13:52 UTC
  • mfrom: (1.1.10) (10.1.5 oneiric-proposed)
  • Revision ID: package-import@ubuntu.com-20130205181352-3kw4f94ilqklzm7c
Tags: 9.1.8-0ubuntu11.10
https://launchpad.net/bugs/1116336
* New upstream security/bug fix release: (LP: #1116336)
  - Prevent execution of enum_recv from SQL
    The function was misdeclared, allowing a simple SQL command to crash the
    server.  In principle an attacker might be able to use it to examine the
    contents of server memory.  Our thanks to Sumit Soni (via Secunia SVCRP)
    for reporting this issue. (CVE-2013-0255)
  - See HISTORY/changelog.gz for the other bug fixes.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/src/sgml/html/warm-standby.html
9
9
REV="MADE"
10
10
HREF="mailto:pgsql-docs@postgresql.org"><LINK
11
11
REL="HOME"
12
 
TITLE="PostgreSQL 9.1.5 Documentation"
 
12
TITLE="PostgreSQL 9.1.8 Documentation"
13
13
HREF="index.html"><LINK
14
14
REL="UP"
15
15
TITLE="High Availability, Load Balancing, and Replication"
26
26
HTTP-EQUIV="Content-Type"
27
27
CONTENT="text/html; charset=ISO-8859-1"><META
28
28
NAME="creation"
29
 
CONTENT="2012-08-14T22:55:48"></HEAD
 
29
CONTENT="2013-02-04T21:38:53"></HEAD
30
30
><BODY
31
31
CLASS="SECT1"
32
32
><DIV
44
44
VALIGN="bottom"
45
45
><A
46
46
HREF="index.html"
47
 
>PostgreSQL 9.1.5 Documentation</A
 
47
>PostgreSQL 9.1.8 Documentation</A
48
48
></TH
49
49
></TR
50
50
><TR
476
476
    generated, without waiting for the WAL file to be filled.
477
477
   </P
478
478
><P
479
 
>    Streaming replication is asynchronous, so there is still a small delay
480
 
    between committing a transaction in the primary and for the changes to
481
 
    become visible in the standby. The delay is however much smaller than with
482
 
    file-based log shipping, typically under one second assuming the standby
483
 
    is powerful enough to keep up with the load. With streaming replication,
484
 
    <TT
 
479
>    Streaming replication is asynchronous by default
 
480
    (see <A
 
481
HREF="warm-standby.html#SYNCHRONOUS-REPLICATION"
 
482
>Section 25.2.6</A
 
483
>), in which case there is
 
484
    a small delay between committing a transaction in the primary and the
 
485
    changes becoming visible in the standby. This delay is however much
 
486
    smaller than with file-based log shipping, typically under one second
 
487
    assuming the standby is powerful enough to keep up with the load. With
 
488
    streaming replication, <TT
485
489
CLASS="VARNAME"
486
490
>archive_timeout</TT
487
 
> is not required to reduce the data loss
488
 
    window.
 
491
> is not required to
 
492
    reduce the data loss window.
489
493
   </P
490
494
><P
491
495
>    If you use streaming replication without file-based continuous