~ubuntu-branches/ubuntu/trusty/postgresql-9.3/trusty-proposed

« back to all changes in this revision

Viewing changes to doc/src/sgml/html/app-pgbasebackup.html

  • Committer: Package Import Robot
  • Author(s): Martin Pitt
  • Date: 2014-07-24 16:13:59 UTC
  • mfrom: (1.1.8)
  • Revision ID: package-import@ubuntu.com-20140724161359-uk325qfv03euxuuh
Tags: 9.3.5-0ubuntu0.14.04.1
* New upstream bug fix release: (LP: #1348176)
  - pg_upgrade: Users who upgraded to version 9.3 using pg_upgrade may have
    an issue with transaction information which causes VACUUM to eventually
    fail. These users should run the script provided in the release notes to
    determine if their installation is affected, and then take the remedy
    steps outlined there.
  - Various data integrity and other bug fixes.
  - Secure Unix-domain sockets of temporary postmasters started during make
    check.
    Any local user able to access the socket file could connect as the
    server's bootstrap superuser, then proceed to execute arbitrary code as
    the operating-system user running the test, as we previously noted in
    CVE-2014-0067. This change defends against that risk by placing the
    server's socket in a temporary, mode 0700 subdirectory of /tmp.
  - See release notes for details:
    http://www.postgresql.org/about/news/1534/
* Remove pg_regress patches to support --host=/path, obsolete with above
  upstream changes and not applicable any more.
* Drop tcl8.6 patch, applied upstream.
* Add missing logrotate test dependency.

Show diffs side-by-side

added added

removed removed

Lines of Context:
9
9
REV="MADE"
10
10
HREF="mailto:pgsql-docs@postgresql.org"><LINK
11
11
REL="HOME"
12
 
TITLE="PostgreSQL 9.3.4 Documentation"
 
12
TITLE="PostgreSQL 9.3.5 Documentation"
13
13
HREF="index.html"><LINK
14
14
REL="UP"
15
15
TITLE="PostgreSQL Client Applications"
26
26
HTTP-EQUIV="Content-Type"
27
27
CONTENT="text/html; charset=ISO-8859-1"><META
28
28
NAME="creation"
29
 
CONTENT="2014-03-17T19:42:29"></HEAD
 
29
CONTENT="2014-07-21T19:26:29"></HEAD
30
30
><BODY
31
31
CLASS="REFENTRY"
32
32
><DIV
44
44
VALIGN="bottom"
45
45
><A
46
46
HREF="index.html"
47
 
>PostgreSQL 9.3.4 Documentation</A
 
47
>PostgreSQL 9.3.5 Documentation</A
48
48
></TH
49
49
></TR
50
50
><TR
95
95
><DIV
96
96
CLASS="REFNAMEDIV"
97
97
><A
98
 
NAME="AEN84101"
 
98
NAME="AEN84105"
99
99
></A
100
100
><H2
101
101
>Name</H2
106
106
><DIV
107
107
CLASS="REFSYNOPSISDIV"
108
108
><A
109
 
NAME="AEN84107"
 
109
NAME="AEN84111"
110
110
></A
111
111
><H2
112
112
>Synopsis</H2
124
124
><DIV
125
125
CLASS="REFSECT1"
126
126
><A
127
 
NAME="AEN84112"
 
127
NAME="AEN84116"
128
128
></A
129
129
><H2
130
130
>   Description
154
154
CLASS="APPLICATION"
155
155
>pg_basebackup</SPAN
156
156
> makes a binary copy of the database
157
 
   cluster files, while making sure the system is automatically put in and
 
157
   cluster files, while making sure the system is put in and
158
158
   out of backup mode automatically. Backups are always taken of the entire
159
 
   database cluster, it is not possible to back up individual databases or
 
159
   database cluster; it is not possible to back up individual databases or
160
160
   database objects. For individual database backups, a tool such as
161
161
   <A
162
162
HREF="app-pgdump.html"
270
270
><DIV
271
271
CLASS="REFSECT1"
272
272
><A
273
 
NAME="AEN84150"
 
273
NAME="AEN84154"
274
274
></A
275
275
><H2
276
276
>Options</H2
958
958
><DIV
959
959
CLASS="REFSECT1"
960
960
><A
961
 
NAME="AEN84387"
 
961
NAME="AEN84391"
962
962
></A
963
963
><H2
964
964
>Environment</H2
980
980
><DIV
981
981
CLASS="REFSECT1"
982
982
><A
983
 
NAME="AEN84393"
 
983
NAME="AEN84397"
984
984
></A
985
985
><H2
986
986
>Notes</H2
1010
1010
><DIV
1011
1011
CLASS="REFSECT1"
1012
1012
><A
1013
 
NAME="AEN84400"
 
1013
NAME="AEN84404"
1014
1014
></A
1015
1015
><H2
1016
1016
>Examples</H2
1076
1076
><DIV
1077
1077
CLASS="REFSECT1"
1078
1078
><A
1079
 
NAME="AEN84418"
 
1079
NAME="AEN84422"
1080
1080
></A
1081
1081
><H2
1082
1082
>See Also</H2