From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-commits+bounces-336093-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1QAL5y-0005PQ-Dt
	for garchives@archives.gentoo.org; Thu, 14 Apr 2011 11:52:22 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 185021C0B3;
	Thu, 14 Apr 2011 11:52:14 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	by pigeon.gentoo.org (Postfix) with ESMTP id CEC8C1C0B3
	for <gentoo-commits@lists.gentoo.org>; Thu, 14 Apr 2011 11:52:13 +0000 (UTC)
Received: from pelican.gentoo.org (unknown [66.219.59.40])
	(using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp.gentoo.org (Postfix) with ESMTPS id 2E4631B4161
	for <gentoo-commits@lists.gentoo.org>; Thu, 14 Apr 2011 11:52:13 +0000 (UTC)
Received: from localhost.localdomain (localhost [127.0.0.1])
	by pelican.gentoo.org (Postfix) with ESMTP id 7EE968006D
	for <gentoo-commits@lists.gentoo.org>; Thu, 14 Apr 2011 11:52:12 +0000 (UTC)
From: "Aaron Swenson" <titanofold@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Content-type: text/plain; charset=UTF-8
Reply-To: gentoo-dev@lists.gentoo.org, "Aaron Swenson" <titanofold@gentoo.org>
Message-ID: <2875b5154e230602ead79ffdb734a04b29756ca3.titanofold@gentoo>
Subject: [gentoo-commits] proj/pgsql-patches:documentation commit in: /
X-VCS-Repository: proj/pgsql-patches
X-VCS-Files: postgresql.xml
X-VCS-Directories: /
X-VCS-Committer: titanofold
X-VCS-Committer-Name: Aaron Swenson
X-VCS-Revision: 2875b5154e230602ead79ffdb734a04b29756ca3
Date: Thu, 14 Apr 2011 11:52:12 +0000 (UTC)
Precedence: bulk
List-Post: <mailto:gentoo-commits@lists.gentoo.org>
List-Help: <mailto:gentoo-commits+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-commits+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-commits+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-commits.gentoo.org>
X-BeenThere: gentoo-commits@lists.gentoo.org
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 
X-Archives-Hash: 8df08983acb22940a6938a1bb05e003f

commit:     2875b5154e230602ead79ffdb734a04b29756ca3
Author:     Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Thu Apr 14 11:51:05 2011 +0000
Commit:     Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Thu Apr 14 11:51:05 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=3Dproj/pgsql-patches=
.git;a=3Dcommit;h=3D2875b515

Clarified some sentences. Renamed 'Controling Access' section to 'pg_hba.=
conf'.

---
 postgresql.xml |   67 ++++++++++++++++++++++----------------------------=
-----
 1 files changed, 27 insertions(+), 40 deletions(-)

diff --git a/postgresql.xml b/postgresql.xml
index 73eb974..c7bac14 100644
--- a/postgresql.xml
+++ b/postgresql.xml
@@ -23,7 +23,7 @@ not supplant it.
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
=20
-<version>7</version>
+<version>8</version>
 <date>2011-03-28</date>
=20
 <chapter>
@@ -72,15 +72,8 @@ commands in this article as necessary for your specifi=
c version.
 </p>
=20
 <impo>
-The 7.4 and 8.0 branch of PostgreSQL had their support dropped in Octobe=
r of
-2010. The 8.1 branch had its support dropped in November of 2010. If you=
 have
-not done so already, you should start <uri link=3D"#migrating">migrating=
</uri> to
-a more recent version of PostgreSQL.
-</impo>
-
-<impo>
-The 8.2 branch will have its support dropped in December of 2011. Start =
planning
-your migration now.
+The 8.2 branch will have its upstream support dropped in December of 201=
1. Start
+planning your migration now.
 </impo>
=20
 </body>
@@ -97,15 +90,16 @@ the same time. This is useful in such circumstances w=
here you need to move data
 from an older database to a new database, or need to have a production a=
nd a
 testing database on the same machine. Also, this prevents a database,
 corresponding libraries or executables from being overwritten by an inco=
mpatible
-update.
+update. That would require migration which is described in this guide.
 </p>
=20
 <p>
 Additionally, bug and security fixes, which are delivered via minor vers=
ion
-updates, can be applied without fear of corrupting data; 9.0.2 can be up=
dated to
-9.0.3 as they are guaranteed to be compatible and require no more intera=
ction
-from you than to emerge it and restart the server process &mdash; neithe=
r
-migration, reconfiguration nor initialization are necessary.
+updates, can be applied without fear of corrupting the database or the
+PostgreSQL installation itself; 9.0.2 can be updated to 9.0.3 as they ar=
e
+guaranteed to be compatible and require no more interaction from you tha=
n to
+emerge it and restart the server process &mdash; neither migration,
+reconfiguration nor initialization are necessary.
 </p>
=20
 <p>
@@ -120,11 +114,11 @@ Versioning Policy</uri> for more information.
 <body>
=20
 <p>
-There is quite a bit that will not be covered. If the <uri
-link=3D"http://www.postgresql.org/docs/">official documentation</uri> we=
re to be
-printed out on 8&frac12;x11 paper, it would be somewhere in the neighbor=
hood of 2,000
-pages. So, a lot of details will be left out in this quick start guide. =
Only
-Gentoo specific issues will be covered and some basic configuration guid=
elines.
+There is quite a bit that will not be covered. The <uri
+link=3D"http://www.postgresql.org/docs/">official documentation</uri> is=
 somewhere
+in the neighborhood of 2,000 pages. So, a lot of details will be left ou=
t in
+this quick start guide. Only Gentoo specific issues will be covered and =
some
+basic configuration guidelines.
 </p>
=20
 </body>
@@ -139,8 +133,9 @@ Gentoo specific issues will be covered and some basic=
 configuration guidelines.
=20
 <p>
 If you have any of the following ebuilds installed, then you have an old=
er,
-obsolete Gentoo installation of PostgreSQL: dev-db/postgresql-libs,=20
-dev-db/postgresql-client, dev-db/libpq and/or dev-db/postgresql.=20
+obsolete Gentoo installation of PostgreSQL and should migrate now:
+dev-db/postgresql-libs, dev-db/postgresql-client, dev-db/libpq and/or
+dev-db/postgresql.
 </p>
=20
 <p>
@@ -452,29 +447,21 @@ This time the focus is upon the files in the <e>PGD=
ATA</e> directory,
 <p>
 This is the main configuration file. The line that you may find of immed=
iate
 interest is <e>listen_addresses</e>. This variable defines to which addr=
esses
-PostgreSQL will bind. By default, only loopback devices and Unix sockets=
 are
-bound; localhost and <path>/var/run/postgresql/.s.PGSQL.5432</path>. Cha=
nging
-<e>listen_addresses</e> is not enough, though, to enable remote
-connections. There is another file that actually controls the connection=
s, which
-is covered in the next subsection. The <uri
+PostgreSQL will bind. By default, only localhost and the Unix socket are
+bound. Changing <e>listen_addresses</e> is not enough to enable remote
+connections. That will be covered in the next section. The <uri
 link=3D"http://www.postgresql.org/docs/current/static/runtime-config.htm=
l">official
 documentation</uri> is fairly easy to understand and is exhaustive on al=
l the
 settings available. It would behoove you to read that in addition to wha=
t is
 covered here as some things may change.
 </p>
=20
-</body>
-</section>
-<section>
-<title>Error Reporting and Logging</title>
-<body>
-
 <p>
 Of secondary interest is the logging destination. By default, everything=
 is
 logged to <path>postmaster.log</path> in the <e>DATA_DIR</e> directory. =
There is
 an entire subsection of <path>postgresql.conf</path> that covers a slew =
of
-options for how and where to log. The section is marked: ERROR REPORTING=
 AND
-LOGGING.
+options for how, what and where to log. The section is marked: ERROR REP=
ORTING
+AND LOGGING.
 </p>
=20
 <p>
@@ -485,14 +472,14 @@ defaults in <path>postgresql.conf</path> are reason=
able enough to get you going.
 </body>
 </section>
 <section>
-<title>Controlling Access</title>
+<title>pg_hba.conf</title>
 <body>
=20
 <p>
-The <path>pg_hba.conf</path> file states who is allowed to and in which =
way they
-may connect to the database. Again, the documentation is quite exhaustiv=
e on the
-settings and what they all mean, but a few things are covered here for
-clarification.
+The <path>pg_hba.conf</path> file states who is allowed to connect to th=
e
+database server and which authentication method must be used to establis=
h the
+connection. Again, the documentation is quite exhaustive on the settings=
 and
+what they all mean, but a few things are covered here for clarification.
 </p>
=20
 <pre caption=3D"Default pg_hba.conf">