* [gentoo-commits] proj/pgsql-patches:documentation commit in: /
@ 2011-03-29 1:17 Aaron Swenson
0 siblings, 0 replies; 11+ messages in thread
From: Aaron Swenson @ 2011-03-29 1:17 UTC (permalink / raw
To: gentoo-commits
commit: daa89b823dcee2f77a0e2a3f26f3c69f0e0f505c
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 27 12:18:00 2011 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Sun Mar 27 12:18:00 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/pgsql-patches.git;a=commit;h=daa89b82
Fixed 80 column width. Prepping to merge suggestions from bug 330927.
---
postgresql.xml | 290 ++++++++++++++++++++++++++-----------------------------
1 files changed, 137 insertions(+), 153 deletions(-)
diff --git a/postgresql.xml b/postgresql.xml
index b4423f3..0cc191a 100644
--- a/postgresql.xml
+++ b/postgresql.xml
@@ -33,11 +33,11 @@ not supplant it.
<body>
<p>
-<uri link="http://www.postgresql.org">PostgreSQL</uri> is a free and open
-source relational database management system (RDBMS). It supports such things
-as transactions, schemata and foreign keys, and is often touted to more
-strictly adhere to the SQL standards and to be more secure, by default, than
-any other database, commercial or otherwise.
+<uri link="http://www.postgresql.org">PostgreSQL</uri> is a free and open source
+relational database management system (RDBMS). It supports such things as
+transactions, schemata and foreign keys, and is often touted to more strictly
+adhere to the SQL standards and to be more secure, by default, than any other
+database, commercial or otherwise.
</p>
</body>
@@ -69,13 +69,13 @@ commands in this article as necessary for your specific version.
<impo>
The 7.4 and 8.0 branch of PostgreSQL had their support dropped in October 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="#migrating">migrating</uri>
-to a more recent version of PostgreSQL.
+not done so already, you should start <uri link="#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 support dropped in December of 2011. Start planning
+your migration now.
</impo>
</body>
@@ -85,21 +85,21 @@ planning your migration now.
<body>
<p>
-The Ebuilds in Portage feature slotting matching the major version. This
-allows you to have two major versions of PostgreSQL operating simultaneously;
-8.4 and 9.0 can serve at the same time. This is useful in such circumstances
-where you need to move data from an older database to a new database, or need
-to have a production and a testing database on the same machine. Also, this
-prevents a database, corresponding libraries or executables from being
-overwritten by an incompatible update.
+The Ebuilds in Portage feature slotting matching the major version. This allows
+you to have two major versions of PostgreSQL operating simultaneously; 8.4 and
+9.0 can serve at the same time. This is useful in such circumstances where you
+need to move data from an older database to a new database, or need to have a
+production and a testing database on the same machine. Also, this prevents a
+database, corresponding libraries or executables from being overwritten by an
+incompatible update.
</p>
<p>
Additionally, bug and security fixes, which are delivered via minor version
-updates, can be applied without fear of corrupting data; 9.0.2 can be updated
-to 9.0.3 as they are guaranteed to be compatible and require no more
-interaction from you than to emerge it and restart the server process —
-no migration, reconfiguration or initialization are necessary.
+updates, can be applied without fear of corrupting data; 9.0.2 can be updated to
+9.0.3 as they are guaranteed to be compatible and require no more interaction
+from you than to emerge it and restart the server process — no migration,
+reconfiguration or initialization are necessary.
</p>
<p>
@@ -115,10 +115,9 @@ Versioning Policy</uri> for more information.
<p>
There is quite a bit that cannot be covered. The <uri
-link="http://www.postgresql.org/docs/">official documentation</uri> is
-somewhere in the neighborhood of 2,000 pages. A lot of details will be left
-out. Only Gentoo specific issues will be covered and some basic configuration
-guidelines.
+link="http://www.postgresql.org/docs/">official documentation</uri> is somewhere
+in the neighborhood of 2,000 pages. A lot of details will be left out. Only
+Gentoo specific issues will be covered and some basic configuration guidelines.
</p>
</body>
@@ -157,9 +156,8 @@ Ebuilds to the new ones.
<tr>
<ti>doc</ti>
<ti>
- Include the documentation. The documentation is the same as can
- be found <uri link="http://www.postgresql.org/docs/">on
- line</uri>.
+ Include the documentation. The documentation is the same as can be found
+ <uri link="http://www.postgresql.org/docs/">on line</uri>.
</ti>
</tr>
<tr>
@@ -169,8 +167,7 @@ Ebuilds to the new ones.
<tr>
<ti>ldap</ti>
<ti>
- Support for utilizing LDAP authentication and connection parameter
- lookup.
+ Support for utilizing LDAP authentication and connection parameter lookup.
</ti>
</tr>
<tr>
@@ -183,8 +180,7 @@ Ebuilds to the new ones.
<tr>
<ti>pam</ti>
<ti>
- Support for utilizing Pluggable Authentication Module for
- authentication.
+ Support for utilizing Pluggable Authentication Module for authentication.
</ti>
</tr>
<tr>
@@ -196,24 +192,21 @@ Ebuilds to the new ones.
<tr>
<ti>pg-intdatetime (Deprecated)</ti>
<ti>
- Use the newer method for formatting time stamps. Unless you had a
- previous installation that utilized the deprecated method, leave this
- enabled.
+ Use the newer method for formatting time stamps. Unless you had a previous
+ installation that utilized the deprecated method, leave this enabled.
</ti>
</tr>
<tr>
<ti>pg_legacytimestamp</ti>
<ti>
- Use the older method for formatting time stamps. Unless you had a
- previous installation that utilized the deprecated method, leave this
- disabled.
+ Use the older method for formatting time stamps. Unless you had a previous
+ installation that utilized the deprecated method, leave this disabled.
</ti>
</tr>
<tr>
<ti>python</ti>
<ti>
- Enable support for using Python to write functions and trigger
- procedures.
+ Enable support for using Python to write functions and trigger procedures.
</ti>
</tr>
<tr>
@@ -284,10 +277,10 @@ Ebuilds to the new ones.
</pre>
<p>
-You may receive a notice regarding that any of the above packages are blocked
-by any or all of the following packages: dev-db/postgresql-libs,
-dev-db/postgresql-client, dev-db/libpq or dev-db/postgresql. These packages
-are <b>not maintained</b> and are <b>ancient</b>. Refer to the section on <uri
+You may receive a notice regarding that any of the above packages are blocked by
+any or all of the following packages: dev-db/postgresql-libs,
+dev-db/postgresql-client, dev-db/libpq or dev-db/postgresql. These packages are
+<b>not maintained</b> and are <b>ancient</b>. Refer to the section on <uri
link="#migrating">migration</uri> for how to handle this situation.
</p>
@@ -305,8 +298,8 @@ directory that contains the database cluster and reinitializing.
</p>
<note>
-The ebuilds are Prefix compatible, so adjust the paths as necessary
-for your set up.
+The ebuilds are Prefix compatible, so adjust the paths as necessary for your set
+up.
</note>
<p>
@@ -319,16 +312,14 @@ as the reasonable defaults are, ahem, reasonable.
</p>
<p>
-In the following example, <e>PGDATA</e> states that the configuration
-files are to be located in
-<path>/etc/postgresql-9.0/</path>. <e>DATA_DIR</e> states that the
-database cluster should be installed to
-<path>/var/lib/postgresql/9.0/data/</path>, which is the default. If
-you decide to stray from the default, bear in mind that it is a
-<b>very good idea</b> to keep the major version in the
-path. <e>PG_INITDB_OPTS</e> states that the default locale should be
-<e>en_US.UTF-8</e>. That is, U.S. English ordering and formatting, and
-UTF-8 character encoding.
+In the following example, <e>PGDATA</e> states that the configuration files are
+to be located in <path>/etc/postgresql-9.0/</path>. <e>DATA_DIR</e> states that
+the database cluster should be installed to
+<path>/var/lib/postgresql/9.0/data/</path>, which is the default. If you decide
+to stray from the default, bear in mind that it is a <b>very good idea</b> to
+keep the major version in the path. <e>PG_INITDB_OPTS</e> states that the
+default locale should be <e>en_US.UTF-8</e>. That is, U.S. English ordering and
+formatting, and UTF-8 character encoding.
</p>
<pre caption="Example contents of /etc/conf.d/postgresql-8.4">
@@ -344,9 +335,9 @@ DATA_DIR="/var/lib/postgresql/9.0/data"
</pre>
<note>
-This only determines the default locale and character encoding. You
-can specify different locales and/or character encodings at database
-creation time (<c>CREATE DATABASE</c>) in the same database cluster.
+This only determines the default locale and character encoding. You can specify
+different locales and/or character encodings at database creation time
+(<c>CREATE DATABASE</c>) in the same database cluster.
</note>
<p>
@@ -389,8 +380,8 @@ following table lists the six options that, if used, are to be formatted as:
</table>
<p>
-So, if you would like the default to be English, but you want messages in,
-say, Swedish, then your <e>PG_INITDB_OPTS</e> would look like so:
+So, if you would like the default to be English, but you want messages in, say,
+Swedish, then your <e>PG_INITDB_OPTS</e> would look like so:
</p>
<pre caption="Example">
@@ -398,20 +389,20 @@ PG_INITDB_OPTS="--locale=en_US.UTF-8 --lc-messages=sv_SE.UTF-8"
</pre>
<p>
-A complete list of language and character encodings supported by the server
-can be found in the documentation, but your system must also support the
-respective languages and character encodings. Compare the output of <c>locale
--a</c> to the <uri
+A complete list of language and character encodings supported by the server can
+be found in the documentation, but your system must also support the respective
+languages and character encodings. Compare the output of <c>locale -a</c> to the
+<uri
link="http://www.postgresql.org/docs/current/static/multibyte.html">encodings</uri>
in the documentation.
</p>
<p>
-You can change your locale and encoding selections at database
-creation time (<uri
+You can change your locale and encoding selections at database creation time
+(<uri
link="http://www.postgresql.org/docs/current/static/sql-createdatabase.html"><c>CREATE
-DATABASE</c></uri>). In order to change the locale for a database
-after you have created it, you must drop the database and start over again.
+DATABASE</c></uri>). In order to change the locale for a database after you have
+created it, you must drop the database and start over again.
</p>
</body>
@@ -461,13 +452,13 @@ interest is <e>listen_addresses</e>. This variable defines to which addresses
PostgreSQL will bind. By default, only loopback devices and Unix sockets are
bound; localhost and <path>/var/run/postgresql/.s.PGSQL.5432</path>. Changing
<e>listen_addresses</e> is not enough, though, to enable remote
-connections. There is another file that actually controls the connections,
-which is covered in the next subsection. The <uri
+connections. There is another file that actually controls the connections, which
+is covered in the next subsection. The <uri
link="http://www.postgresql.org/docs/current/static/runtime-config.html">official
documentation</uri> is fairly easy to understand and is exhaustive on all the
-settings available. It would behoove you to read that rather than it be
-covered here as some things may change, and this author would not be able to
-clarify it any further.
+settings available. It would behoove you to read that rather than it be covered
+here as some things may change, and this author would not be able to clarify it
+any further.
</p>
</body>
@@ -478,16 +469,15 @@ clarify it any further.
<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
+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.
</p>
<p>
Other than <e>listen_addresses</e> and the logging options, the rest of the
-defaults in <path>postgresql.conf</path> are reasonable enough to get you
-going.
+defaults in <path>postgresql.conf</path> are reasonable enough to get you going.
</p>
</body>
@@ -497,9 +487,9 @@ going.
<body>
<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 exhaustive
-on the settings and what they all mean, but a few things are covered here for
+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 exhaustive on the
+settings and what they all mean, but a few things are covered here for
clarification.
</p>
@@ -515,62 +505,60 @@ host all all ::1/128 trust
</pre>
<p>
-As has been mentioned before, by default the server is secure. Kind of. There
-is only one database role that is available for log in by default,
-<e>postgres</e>, and the only way to initiate a connection to the database is
-through the <path>/var/run/postgresql/.s.PGSQL.5432</path> Unix socket, which
-is owned by the <e>postgres</e> system user and system group, or via
-localhost. Now for the "kind of" bit: Any user on the system can make a
-connection to the database through the localhost. Even as the <e>postgres</e>
-database superuser.
+As has been mentioned before, by default the server is secure. Kind of. There is
+only one database role that is available for log in by default, <e>postgres</e>,
+and the only way to initiate a connection to the database is through the
+<path>/var/run/postgresql/.s.PGSQL.5432</path> Unix socket, which is owned by
+the <e>postgres</e> system user and system group, or via localhost. Now for the
+"kind of" bit: Any user on the system can make a connection to the database
+through the localhost. Even as the <e>postgres</e> database superuser.
</p>
<p>
To make a connection through the Unix socket, however, the users —
-including the users for other services such as <e>apache</e> — must be
-in the <e>postgres</e> system group. Use <c>usermod -a -G postgres
-<e>user</e></c> to add <e>user</e> to the <e>postgres</e> group. Users not in
-the <e>postgres</e> group will be rejected with: Permission denied.
+including the users for other services such as <e>apache</e> — must be in
+the <e>postgres</e> system group. Use <c>usermod -a -G postgres <e>user</e></c>
+to add <e>user</e> to the <e>postgres</e> group. Users not in the
+<e>postgres</e> group will be rejected with: Permission denied.
</p>
<warn>
-Never disable the Unix socket entirely. The initscripts require access to it
-in order to operate properly. The method can be changed without consequence.
+Never disable the Unix socket entirely. The initscripts require access to it in
+order to operate properly. The method can be changed without consequence.
</warn>
<p>
-The <e>trust</e> method is what allows any user to log on as any user without
-a password. It specifies just what it implies: Trust all connections for the
-given type to the given database from the given database user, not the system
-user, from the given location without a password. This is what allows any user
-on the system to log on as any user through the localhost connection from the
-get go. This is not as dangerous as it seems, but does pose a serious security
-risk in most circumstances.
+The <e>trust</e> method is what allows any user to log on as any user without a
+password. It specifies just what it implies: Trust all connections for the given
+type to the given database from the given database user, not the system user,
+from the given location without a password. This is what allows any user on the
+system to log on as any user through the localhost connection from the get
+go. This is not as dangerous as it seems, but does pose a serious security risk
+in most circumstances.
</p>
<p>
The two methods you will most likely use are: <e>password</e> and
<e>md5</e>. The password method only specifies that a password is required to
start the connection and the password is sent "in-the-clear". This method is
-fine when such information will never leave the machine, such as connecting
-via the Unix socket or localhost. The md5 method is like password, but
-requires the password to be encrypted using an md5 hash. This is what you
-want to use whenever the password is going to traverse a network.
+fine when such information will never leave the machine, such as connecting via
+the Unix socket or localhost. The md5 method is like password, but requires the
+password to be encrypted using an md5 hash. This is what you want to use
+whenever the password is going to traverse a network.
</p>
<p>
At this point, this author would like to bring your attention to the last two
lines, four lines including comments, of the <path>pg_hba.conf</path>
-file. PostgreSQL has native support for IPv6 regardless of your desires for
-such support. Additionally, IPv4 addresses are automatically mapped to IPv6
+file. PostgreSQL has native support for IPv6 regardless of your desires for such
+support. Additionally, IPv4 addresses are automatically mapped to IPv6
addresses, <e>id est</e>, 127.0.0.1 will be mapped to ::FFFF:127.0.0.1 and as
"pure" IPv6 ::FFFF:7F00:0001.
</p>
<p>
-There seems to be some misunderstanding, though, as to how host names are
-mapped to IP addresses. Let us take a look at the <path>/etc/hosts</path>
-file.
+There seems to be some misunderstanding, though, as to how host names are mapped
+to IP addresses. Let us take a look at the <path>/etc/hosts</path> file.
</p>
<pre caption="Example /etc/hosts">
@@ -580,22 +568,22 @@ file.
</pre>
<p>
-From the example above you can see that both an IPv4 and an IPv6 IP address
-are mapped to localhost. When <c>psql</c> refers to this file, it will grab
-the first match and use that as the address; in this case 127.0.0.1. When
-PostgreSQL parses this, it will match the IPv6 formatted address as well,
+From the example above you can see that both an IPv4 and an IPv6 IP address are
+mapped to localhost. When <c>psql</c> refers to this file, it will grab the
+first match and use that as the address; in this case 127.0.0.1. When PostgreSQL
+parses this, it will match the IPv6 formatted address as well,
e.g. ::ffff:127.0.0.1. If, however, the IPv6 address appears first, then
<c>psql</c> will map to ::1 alone; ::1 is not the same as ::ffff:127.0.0.1. As
such, if you do not have ::1 as a permitted means of access, <c>psql</c> will
-not be able to establish a connection. Furthermore, your kernel needs to
-support the IPv6 protocol.
+not be able to establish a connection. Furthermore, your kernel needs to support
+the IPv6 protocol.
</p>
<p>
So, it is better to specify IP addresses alone to <c>psql</c> and in
<path>pg_hba.conf</path> rather than to rely on <path>/etc/hosts</path> to be
-ordered properly, and it removes any doubt as to which IP addresses are
-allowed or to which server you will connect.
+ordered properly, and it removes any doubt as to which IP addresses are allowed
+or to which server you will connect.
</p>
</body>
@@ -675,16 +663,16 @@ dev-db/postgresql-docs, dev-db/postgresql-base and dev-db/postgresql-server.
<body>
<p>
-<e>pg_upgrade</e>, a new utility that comes along with 9.0 and later,
-simplifies the migration process rather drastically.
+<e>pg_upgrade</e>, a new utility that comes along with 9.0 and later, simplifies
+the migration process rather drastically.
</p>
<p>
However, there are two caveats with using pg_upgrade. Firstly, it does not
-support configuration files being in a different directory than where the
-data is stored. This is resolved by using a symbolic link. Lastly, you can
-only use it to migrate from a database from 8.3 or newer. If you have an
-older database you will need to follow the "Pre-9.0 Migration" instructions.
+support configuration files being in a different directory than where the data
+is stored. This is resolved by using a symbolic link. Lastly, you can only use
+it to migrate from a database from 8.3 or newer. If you have an older database
+you will need to follow the "Pre-9.0 Migration" instructions.
</p>
<pre caption="Migrating with pg_upgrade">
@@ -719,28 +707,26 @@ hours.
<p>
In the following examples, it is assumed that you've stuck with the default
-locations and port settings, and that you are migrating from 8.3 to
-8.4. Adjust accordingly if you have deviated from the default.
+locations and port settings, and that you are migrating from 8.3 to 8.4. Adjust
+accordingly if you have deviated from the default.
</p>
<p>
-If you have not already done so, follow the <uri
-link="#doc_chap1">installation instructions</uri> before starting the
-migration. Such a compile may hamper performance on the database server, but
-it can keep going.
+If you have not already done so, follow the <uri link="#doc_chap1">installation
+instructions</uri> before starting the migration. Such a compile may hamper
+performance on the database server, but it can keep going.
</p>
<p>
A couple files need to be tweaked before beginning the migration. Edit
-<e>PGPORT</e> in the <path>/etc/conf.d/postgresql-8.4</path> configuration
-file to 6543. (Any port number other than what your old installation is bound
-to will do.)
+<e>PGPORT</e> in the <path>/etc/conf.d/postgresql-8.4</path> configuration file
+to 6543. (Any port number other than what your old installation is bound to will
+do.)
</p>
<p>
-Then edit <path>/etc/postgresql-8.3/pg_hba.conf</path> so that only the
-database superuser <e>postgres</e> can access the database cluster via the
-Unix socket.
+Then edit <path>/etc/postgresql-8.3/pg_hba.conf</path> so that only the database
+superuser <e>postgres</e> can access the database cluster via the Unix socket.
</p>
<pre caption="Migrate with the New Ebuilds">
@@ -769,9 +755,8 @@ Unix socket.
</pre>
<p>
-Hopefully everything went according to plan and you have a successfully
-updated server that contains precisely the same data, bit for bit, as the old
-server.
+Hopefully everything went according to plan and you have a successfully updated
+server that contains precisely the same data, bit for bit, as the old server.
</p>
</body>
@@ -782,16 +767,16 @@ server.
<p>
You will need to schedule some downtime for your server. The old Ebuilds
-<b>cannot</b> be installed at the same time as the new Ebuilds. As such,
-assume that the server will have to be down for a few hours. Maybe for the
-weekend, even.
+<b>cannot</b> be installed at the same time as the new Ebuilds. As such, assume
+that the server will have to be down for a few hours. Maybe for the weekend,
+even.
</p>
<p>
-Before starting, you will need to deny access to the server, so that no
-changes are made. You may also want to backup your
-<path>postgresql.conf</path> and <path>pg_hba.conf</path> and any other
-configuration file that you deem important.
+Before starting, you will need to deny access to the server, so that no changes
+are made. You may also want to backup your <path>postgresql.conf</path> and
+<path>pg_hba.conf</path> and any other configuration file that you deem
+important.
</p>
<pre caption="Steps to Migrate from the Obsolete Ebuilds">
@@ -808,10 +793,10 @@ server.)
</pre>
<p>
-You may break some packages that were built against those ancient packages,
-but once you have installed dev-db/postgresql-base and/or
-dev-db/postgresql-server you can run <c>revdep-rebuild</c> to reemerge any
-packages that may have been broken.
+You may break some packages that were built against those ancient packages, but
+once you have installed dev-db/postgresql-base and/or dev-db/postgresql-server
+you can run <c>revdep-rebuild</c> to reemerge any packages that may have been
+broken.
</p>
</body>
@@ -825,7 +810,7 @@ packages that may have been broken.
<body>
<p>
-<uri link="http://www.pgadmin.org/"> pgAdmin III</uri> is a graphical utility
+<uri link="http://www.pgadmin.org/">pgAdmin III</uri> is a graphical utility
for managing PostgreSQL.
</p>
@@ -861,8 +846,7 @@ command:
<body>
<p>
-If you get an error upon emerging dev-db/postgresql-base that reads as
-follows:
+If you get an error upon emerging dev-db/postgresql-base that reads as follows:
</p>
<pre caption="Thread Test Program Failed Error Message">
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [gentoo-commits] proj/pgsql-patches:documentation commit in: /
@ 2011-03-29 1:17 Aaron Swenson
0 siblings, 0 replies; 11+ messages in thread
From: Aaron Swenson @ 2011-03-29 1:17 UTC (permalink / raw
To: gentoo-commits
commit: f8317be1c97202f4edecef8f21c074cd50843cf8
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 29 01:16:06 2011 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Tue Mar 29 01:16:06 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/pgsql-patches.git;a=commit;h=f8317be1
Merged changes from bug 330927.
https://bugs.gentoo.org/attachment.cgi?id=264045
---
postgresql.xml | 289 +++++++++++++++++++++++++++----------------------------
1 files changed, 142 insertions(+), 147 deletions(-)
diff --git a/postgresql.xml b/postgresql.xml
index 0cc191a..5ab1044 100644
--- a/postgresql.xml
+++ b/postgresql.xml
@@ -24,7 +24,7 @@ not supplant it.
<license/>
<version>7</version>
-<date>2010-08-02</date>
+<date>2011-03-28</date>
<chapter>
<title>Introduction</title>
@@ -85,21 +85,22 @@ your migration now.
<body>
<p>
-The Ebuilds in Portage feature slotting matching the major version. This allows
-you to have two major versions of PostgreSQL operating simultaneously; 8.4 and
-9.0 can serve at the same time. This is useful in such circumstances where you
-need to move data from an older database to a new database, or need to have a
-production and a testing database on the same machine. Also, this prevents a
-database, corresponding libraries or executables from being overwritten by an
-incompatible update.
+The PostgreSQL ebuilds in Portage feature slotting based on the major version.
+This allows you to have two major versions of PostgreSQL operating
+simultaneously; 8.4 and 9.0 libraries and servers can be installed and server at
+the same time. This is useful in such circumstances where you need to move data
+from an older database to a new database, or need to have a production and a
+testing database on the same machine. Also, this prevents a database,
+corresponding libraries or executables from being overwritten by an incompatible
+update.
</p>
<p>
Additionally, bug and security fixes, which are delivered via minor version
updates, can be applied without fear of corrupting data; 9.0.2 can be updated to
9.0.3 as they are guaranteed to be compatible and require no more interaction
-from you than to emerge it and restart the server process — no migration,
-reconfiguration or initialization are necessary.
+from you than to emerge it and restart the server process — neither
+migration, reconfiguration nor initialization are necessary.
</p>
<p>
@@ -114,32 +115,33 @@ Versioning Policy</uri> for more information.
<body>
<p>
-There is quite a bit that cannot be covered. The <uri
+There is quite a bit that will not be covered. The <uri
link="http://www.postgresql.org/docs/">official documentation</uri> is somewhere
-in the neighborhood of 2,000 pages. A lot of details will be left out. Only
-Gentoo specific issues will be covered and some basic configuration guidelines.
+in the neighborhood 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 guidelines.
</p>
</body>
</section>
</chapter>
-<chapter>
+<chapter id="installation">
<title>Installation</title>
<section>
<title>The Obsolete Ebuilds</title>
<body>
<p>
-The obsolete Ebuilds are: dev-db/postgresql-libs, dev-db/postgresql-client,
-dev-db/libpq and dev-db/postgresql. The new Ebuilds are incompatible with the
-old Ebuilds. Entirely, completely, disastrously.
+If you have any of the following ebuilds installed, then you have an older,
+obsolete Gentoo installation of PostgreSQL: dev-db/postgresql-libs,
+dev-db/postgresql-client, dev-db/libpq and/or dev-db/postgresql.
</p>
<p>
This article does cover <uri link="#migrating">migrating</uri> from an old
-database to a new one. Including the steps needed for migrating from the old
-Ebuilds to the new ones.
+database to a new one, and includes the steps needed for migrating from the old
+ebuilds to the new ones.
</p>
</body>
@@ -150,111 +152,112 @@ Ebuilds to the new ones.
<table>
<tr>
- <th>USE Flag</th>
- <th>Meaning</th>
+ <th>USE Flag</th>
+ <th>Meaning</th>
</tr>
<tr>
- <ti>doc</ti>
- <ti>
- Include the documentation. The documentation is the same as can be found
- <uri link="http://www.postgresql.org/docs/">on line</uri>.
- </ti>
+ <ti>doc</ti>
+ <ti>
+ Include the <uri
+ link="http://www.postgresql.org/docs/">online documentation</uri> to be
+ stored on your system
+ </ti>
</tr>
<tr>
- <ti>kerberos</ti>
- <ti>Support for utilizing Kerberos for authentication.</ti>
+ <ti>kerberos</ti>
+ <ti>Support for utilizing Kerberos for authentication.</ti>
</tr>
<tr>
- <ti>ldap</ti>
- <ti>
- Support for utilizing LDAP authentication and connection parameter lookup.
- </ti>
+ <ti>ldap</ti>
+ <ti>
+ Support for utilizing LDAP authentication and connection parameter lookup.
+ </ti>
</tr>
<tr>
- <ti>nls</ti>
- <ti>
- Enable the ability to display messages in a language other than
- English. Used in conjunction with the Portage variable LINGUAS.
- </ti>
+ <ti>nls</ti>
+ <ti>
+ Enable the ability to display messages in a language other than
+ English. Used in conjunction with the Portage variable LINGUAS.
+ </ti>
</tr>
<tr>
- <ti>pam</ti>
- <ti>
- Support for utilizing Pluggable Authentication Module for authentication.
- </ti>
+ <ti>pam</ti>
+ <ti>
+ Support for utilizing Pluggable Authentication Modules for authentication.
+ </ti>
</tr>
<tr>
- <ti>perl</ti>
- <ti>
- Enable support for using Perl to write functions and trigger procedures.
- </ti>
+ <ti>perl</ti>
+ <ti>
+ Enable support for using Perl to write functions and trigger procedures.
+ </ti>
</tr>
<tr>
- <ti>pg-intdatetime (Deprecated)</ti>
- <ti>
- Use the newer method for formatting time stamps. Unless you had a previous
- installation that utilized the deprecated method, leave this enabled.
- </ti>
+ <ti>pg-intdatetime (Deprecated)</ti>
+ <ti>
+ Use the newer method for formatting time stamps. Unless you had a previous
+ installation that utilized the deprecated method, leave this enabled.
+ </ti>
</tr>
<tr>
- <ti>pg_legacytimestamp</ti>
- <ti>
- Use the older method for formatting time stamps. Unless you had a previous
- installation that utilized the deprecated method, leave this disabled.
- </ti>
+ <ti>pg_legacytimestamp</ti>
+ <ti>
+ Use the older method for formatting time stamps. Unless you had a previous
+ installation that utilized the deprecated method, leave this disabled.
+ </ti>
</tr>
<tr>
- <ti>python</ti>
- <ti>
- Enable support for using Python to write functions and trigger procedures.
- </ti>
+ <ti>python</ti>
+ <ti>
+ Enable support for using Python to write functions and trigger procedures.
+ </ti>
</tr>
<tr>
- <ti>readline</ti>
- <ti>
- You really want this enabled. Disabling removes command line editing and
- history in psql.
- </ti>
+ <ti>readline</ti>
+ <ti>
+ You really want this enabled. Disabling removes command line editing and
+ history in psql.
+ </ti>
</tr>
<tr>
- <ti>selinux</ti>
- <ti>
- Install respective SELinux policy. This can only be enabled by using the
- SELinux profile.
- </ti>
+ <ti>selinux</ti>
+ <ti>
+ Install respective SELinux policy. This can only be enabled by using the
+ SELinux profile.
+ </ti>
</tr>
<tr>
- <ti>ssl</ti>
- <ti>Enable support for SSL connections.</ti>
+ <ti>ssl</ti>
+ <ti>Enable support for SSL connections.</ti>
</tr>
<tr>
- <ti>tcl</ti>
- <ti>
- Enable support for using Tcl to write functions and trigger procedures.
- </ti>
+ <ti>tcl</ti>
+ <ti>
+ Enable support for using Tcl to write functions and trigger procedures.
+ </ti>
</tr>
<tr>
- <ti>threads</ti>
- <ti>
- Make the client libraries thread-safe. The rest of your system must be
- thread-safe as well.
- </ti>
+ <ti>threads</ti>
+ <ti>
+ Make the client libraries thread-safe. The rest of your system must be
+ thread-safe as well.
+ </ti>
</tr>
<tr>
- <ti>uuid</ti>
- <ti>
- Include support to generate a 128 bit random unique identifier. This is
- useful for merging databases together as the chances of collision are
- extremely low.
- </ti>
+ <ti>uuid</ti>
+ <ti>
+ Include support to generate a 128 bit random unique identifier. This is
+ useful for merging databases together so the chances of collisions become
+ extremely low.
+ </ti>
</tr>
<tr>
- <ti>xml</ti>
- <ti>Enable SQL/XML support.</ti>
+ <ti>xml</ti>
+ <ti>Enable SQL/XML support.</ti>
</tr>
<tr>
- <ti>zlib</ti>
- <ti>Support for compressed archives in pg_dump and pg_restore.</ti>
+ <ti>zlib</ti>
+ <ti>Support for compressed archives in pg_dump and pg_restore.</ti>
</tr>
</table>
@@ -269,18 +272,18 @@ Ebuilds to the new ones.
[ebuild N ] dev-db/postgresql-docs-9.0.3 0 kB
[ebuild N ]dev-db/postgresql-base-9.0.3 USE="doc nls pam readline ssl zlib
--kerberos -ldap -pg_legacytimestamp -threads" LINGUAS="-af -cs -de -es -fa -fr
--hr -hu -it -ko -nb -pl -pt_BR -ro -ru -sk -sl -sv -tr -zh_CN -zh_TW" 0 kB
+ -kerberos -ldap -pg_legacytimestamp -threads" LINGUAS="-af -cs -de -es -fa -fr
+ -hr -hu -it -ko -nb -pl -pt_BR -ro -ru -sk -sl -sv -tr -zh_CN -zh_TW" 0 kB
[ebuild N ] dev-db/postgresql-server-9.0.3 USE="doc nls perl python
--pg_legacytimestamp (-selinux) -tcl -uuid -xml" LINGUAS="-af -cs -de -es -fa -fr
--hr -hu -it -ko -nb -pl -pt_BR -ro -ru -sk -sl -sv -tr -zh_CN -zh_TW" 0 kB
+ -pg_legacytimestamp (-selinux) -tcl -uuid -xml" LINGUAS="-af -cs -de -es -fa
+ -fr -hr -hu -it -ko -nb -pl -pt_BR -ro -ru -sk -sl -sv -tr -zh_CN -zh_TW" 0 kB
</pre>
<p>
You may receive a notice regarding that any of the above packages are blocked by
any or all of the following packages: dev-db/postgresql-libs,
dev-db/postgresql-client, dev-db/libpq or dev-db/postgresql. These packages are
-<b>not maintained</b> and are <b>ancient</b>. Refer to the section on <uri
+<b>not maintained</b> and obsoleted. Refer to the section on <uri
link="#migrating">migration</uri> for how to handle this situation.
</p>
@@ -297,11 +300,6 @@ defaults of the server and <b>cannot</b> be changed later without deleting the
directory that contains the database cluster and reinitializing.
</p>
-<note>
-The ebuilds are Prefix compatible, so adjust the paths as necessary for your set
-up.
-</note>
-
<p>
<e>PGDATA</e> defines where to place the configuration files. <e>DATA_DIR</e>
defines where to create the database cluster and related
@@ -348,12 +346,12 @@ following table lists the six options that, if used, are to be formatted as:
<table>
<tr>
- <th>Option</th>
- <th>Effects</th>
+ <th>Option</th>
+ <th>Effects</th>
</tr>
<tr>
- <ti>lc-collate</ti>
- <ti>String sort order</ti>
+ <ti>lc-collate</ti>
+ <ti>String sort order</ti>
</tr>
<tr>
<ti>lc-ctype</ti>
@@ -362,20 +360,20 @@ following table lists the six options that, if used, are to be formatted as:
</ti>
</tr>
<tr>
- <ti>lc-messages</ti>
- <ti>Language of messages</ti>
+ <ti>lc-messages</ti>
+ <ti>Language of messages</ti>
</tr>
<tr>
- <ti>lc-monetary</ti>
- <ti>Formatting of currency amounts</ti>
+ <ti>lc-monetary</ti>
+ <ti>Formatting of currency amounts</ti>
</tr>
<tr>
- <ti>lc-numeric</ti>
- <ti>Formatting of numbers</ti>
+ <ti>lc-numeric</ti>
+ <ti>Formatting of numbers</ti>
</tr>
<tr>
- <ti>lc-time</ti>
- <ti>Formatting of dates and times</ti>
+ <ti>lc-time</ti>
+ <ti>Formatting of dates and times</ti>
</tr>
</table>
@@ -436,7 +434,7 @@ into <e>DATA_DIR</e>.
<p>
This time the focus is upon the files in the <e>PGDATA</e> directory
-<path>/etc/postgresql-9.0/</path> instead. Primarily, the
+<path>/etc/postgresql-8.4</path> instead with primary focus on the
<path>postgresql.conf</path> and <path>pg_hba.conf</path> files.
</p>
@@ -456,9 +454,8 @@ connections. There is another file that actually controls the connections, which
is covered in the next subsection. The <uri
link="http://www.postgresql.org/docs/current/static/runtime-config.html">official
documentation</uri> is fairly easy to understand and is exhaustive on all the
-settings available. It would behoove you to read that rather than it be covered
-here as some things may change, and this author would not be able to clarify it
-any further.
+settings available. It would behoove you to read that in addition to what is
+covered here as some things may change.
</p>
</body>
@@ -506,31 +503,31 @@ host all all ::1/128 trust
<p>
As has been mentioned before, by default the server is secure. Kind of. There is
-only one database role that is available for log in by default, <e>postgres</e>,
-and the only way to initiate a connection to the database is through the
-<path>/var/run/postgresql/.s.PGSQL.5432</path> Unix socket, which is owned by
-the <e>postgres</e> system user and system group, or via localhost. Now for the
-"kind of" bit: Any user on the system can make a connection to the database
-through the localhost. Even as the <e>postgres</e> database superuser.
+only one database role that is available for log in by default:
+<e>postgres</e>. And, the only way to initiate a connection to the database is
+through the <path>/var/run/postgresql/.s.PGSQL.5432</path> Unix socket, which is
+owned by the <e>postgres</e> system user and system group, or via localhost. Now
+for the "kind of" bit: Any user on the system can make a connection to the
+database through the localhost. Even as the <e>postgres</e> database superuser.
</p>
<p>
To make a connection through the Unix socket, however, the users —
including the users for other services such as <e>apache</e> — must be in
-the <e>postgres</e> system group. Use <c>usermod -a -G postgres <e>user</e></c>
+the <e>postgres</e> system group. Use <c>gpasswd -a <e>user</e> postgres</c>
to add <e>user</e> to the <e>postgres</e> group. Users not in the
-<e>postgres</e> group will be rejected with: Permission denied.
+<e>postgres</e> group will be rejected with "Permission denied".
</p>
<warn>
Never disable the Unix socket entirely. The initscripts require access to it in
-order to operate properly. The method can be changed without consequence.
+order to operate properly. The method can be changed freely.
</warn>
<p>
The <e>trust</e> method is what allows any user to log on as any user without a
password. It specifies just what it implies: Trust all connections for the given
-type to the given database from the given database user, not the system user,
+type to the given database from the given database user (but not the system user)
from the given location without a password. This is what allows any user on the
system to log on as any user through the localhost connection from the get
go. This is not as dangerous as it seems, but does pose a serious security risk
@@ -542,9 +539,9 @@ The two methods you will most likely use are: <e>password</e> and
<e>md5</e>. The password method only specifies that a password is required to
start the connection and the password is sent "in-the-clear". This method is
fine when such information will never leave the machine, such as connecting via
-the Unix socket or localhost. The md5 method is like password, but requires the
-password to be encrypted using an md5 hash. This is what you want to use
-whenever the password is going to traverse a network.
+the Unix socket or localhost. The md5 method is like password, but protects the
+password by using an md5 hash. This is what you want to use whenever the password
+is going to traverse a network.
</p>
<p>
@@ -552,7 +549,7 @@ At this point, this author would like to bring your attention to the last two
lines, four lines including comments, of the <path>pg_hba.conf</path>
file. PostgreSQL has native support for IPv6 regardless of your desires for such
support. Additionally, IPv4 addresses are automatically mapped to IPv6
-addresses, <e>id est</e>, 127.0.0.1 will be mapped to ::FFFF:127.0.0.1 and as
+addresses, <e>i.e.</e>, 127.0.0.1 will be mapped to ::FFFF:127.0.0.1 and as
"pure" IPv6 ::FFFF:7F00:0001.
</p>
@@ -645,8 +642,8 @@ databases, schemata and all that fun and useful stuff.
<p>
You only need to perform a migration when moving from one major version to
-another, <e>exempli gratia</e>, from PostgreSQL 8.4.7 to 9.0.3, but not from
-9.0.2 to 9.0.3.
+another, <e>e.g.</e>, from PostgreSQL 8.4.7 to 9.0.3, but not from 9.0.2 to
+9.0.3.
</p>
<note>
@@ -700,33 +697,35 @@ you will need to follow the "Pre-9.0 Migration" instructions.
<body>
<p>
-Because the new Ebuilds feature a more advanced slotting method than the
-previous ones, the downtime is quite minimal. Most likely minutes rather than
+Because the new ebuilds feature a more advanced slotting method than the
+previous ones, the downtime is quite minimal, most likely minutes rather than
hours.
</p>
<p>
-In the following examples, it is assumed that you've stuck with the default
+In the following examples, it is assumed that you are using the default
locations and port settings, and that you are migrating from 8.3 to 8.4. Adjust
accordingly if you have deviated from the default.
</p>
<p>
-If you have not already done so, follow the <uri link="#doc_chap1">installation
-instructions</uri> before starting the migration. Such a compile may hamper
-performance on the database server, but it can keep going.
+If you have not already done so, follow the <uri
+link="#installation">installation instructions</uri> before starting the
+migration. Such a compile may hamper performance on the database server
+but it can keep going.
</p>
<p>
-A couple files need to be tweaked before beginning the migration. Edit
+A couple of files need to be tweaked before beginning the migration. Edit
<e>PGPORT</e> in the <path>/etc/conf.d/postgresql-8.4</path> configuration file
to 6543. (Any port number other than what your old installation is bound to will
do.)
</p>
<p>
-Then edit <path>/etc/postgresql-8.3/pg_hba.conf</path> so that only the database
-superuser <e>postgres</e> can access the database cluster via the Unix socket.
+Next, edit <path>/etc/postgresql-8.3/pg_hba.conf</path> so that only the
+database superuser <e>postgres</e> can access the database cluster via the Unix
+socket.
</p>
<pre caption="Migrate with the New Ebuilds">
@@ -766,7 +765,7 @@ server that contains precisely the same data, bit for bit, as the old server.
<body>
<p>
-You will need to schedule some downtime for your server. The old Ebuilds
+You will need to schedule some downtime for your server. The old ebuilds
<b>cannot</b> be installed at the same time as the new Ebuilds. As such, assume
that the server will have to be down for a few hours. Maybe for the weekend,
even.
@@ -814,10 +813,6 @@ broken.
for managing PostgreSQL.
</p>
-<pre>
-# <i>emerge -av pgadmin3</i>
-</pre>
-
</body>
</section>
</chapter>
@@ -863,7 +858,7 @@ guarantee thread safety.
</pre>
<p>
-The solution, in most cases, is to update Sandbox to a version greater than or
+The solution, in most cases, is to update sandbox to a version greater than or
equal to 2.0.
</p>
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [gentoo-commits] proj/pgsql-patches:documentation commit in: /
@ 2011-04-03 12:03 Aaron Swenson
0 siblings, 0 replies; 11+ messages in thread
From: Aaron Swenson @ 2011-04-03 12:03 UTC (permalink / raw
To: gentoo-commits
commit: 8e4c5ff3874a008e2832983612525179af5a7e6c
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 3 12:03:07 2011 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Sun Apr 3 12:03:07 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/pgsql-patches.git;a=commit;h=8e4c5ff3
Tweaked a bit here and there.
---
postgresql.xml | 42 +++++++++++++++++++++++-------------------
1 files changed, 23 insertions(+), 19 deletions(-)
diff --git a/postgresql.xml b/postgresql.xml
index 5ab1044..73eb974 100644
--- a/postgresql.xml
+++ b/postgresql.xml
@@ -40,6 +40,11 @@ adhere to the SQL standards and to be more secure, by default, than any other
database, commercial or otherwise.
</p>
+<p>
+Visit the <uri link="http://www.postgresql.org/about/">About</uri> page on
+postgresql.org for more information.
+</p>
+
</body>
</section>
<section>
@@ -85,9 +90,9 @@ your migration now.
<body>
<p>
-The PostgreSQL ebuilds in Portage feature slotting based on the major version.
-This allows you to have two major versions of PostgreSQL operating
-simultaneously; 8.4 and 9.0 libraries and servers can be installed and server at
+The PostgreSQL ebuilds in Portage feature slotting based on the major version.
+This allows you to have two major versions of PostgreSQL operating
+simultaneously; 8.4 and 9.0 libraries and servers can be installed and serve at
the same time. This is useful in such circumstances where you need to move data
from an older database to a new database, or need to have a production and a
testing database on the same machine. Also, this prevents a database,
@@ -115,11 +120,11 @@ Versioning Policy</uri> for more information.
<body>
<p>
-There is quite a bit that will not be covered. The <uri
-link="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 out in
-this quick start guide. Only Gentoo specific issues will be covered and some
-basic configuration guidelines.
+There is quite a bit that will not be covered. If the <uri
+link="http://www.postgresql.org/docs/">official documentation</uri> were to be
+printed out on 8½x11 paper, it would be somewhere in the neighborhood 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 guidelines.
</p>
</body>
@@ -414,7 +419,7 @@ To finish the installation:
</p>
<pre caption="Finalize the installation">
-# <i>emerge --config =dev-db/postgresql-server:9.0</i>
+# <i>emerge --config dev-db/postgresql-server:9.0</i>
</pre>
<p>
@@ -433,8 +438,8 @@ into <e>DATA_DIR</e>.
<body>
<p>
-This time the focus is upon the files in the <e>PGDATA</e> directory
-<path>/etc/postgresql-8.4</path> instead with primary focus on the
+This time the focus is upon the files in the <e>PGDATA</e> directory,
+<path>/etc/postgresql-9.0</path>, instead with primary focus on the
<path>postgresql.conf</path> and <path>pg_hba.conf</path> files.
</p>
@@ -647,9 +652,9 @@ another, <e>e.g.</e>, from PostgreSQL 8.4.7 to 9.0.3, but not from 9.0.2 to
</p>
<note>
-You will need to migrate your database when you move from the obsolete Ebuilds
+You will need to migrate your database when you move from the obsolete ebuilds
— dev-db/libpq, dev-db/postgresql, dev-db/postgresql-libs, and
-dev-db/postgresql-client — to the new Ebuilds —
+dev-db/postgresql-client — to the new ebuilds —
dev-db/postgresql-docs, dev-db/postgresql-base and dev-db/postgresql-server.
</note>
@@ -766,7 +771,7 @@ server that contains precisely the same data, bit for bit, as the old server.
<p>
You will need to schedule some downtime for your server. The old ebuilds
-<b>cannot</b> be installed at the same time as the new Ebuilds. As such, assume
+<b>cannot</b> be installed at the same time as the new ebuilds. As such, assume
that the server will have to be down for a few hours. Maybe for the weekend,
even.
</p>
@@ -792,10 +797,9 @@ server.)
</pre>
<p>
-You may break some packages that were built against those ancient packages, but
-once you have installed dev-db/postgresql-base and/or dev-db/postgresql-server
-you can run <c>revdep-rebuild</c> to reemerge any packages that may have been
-broken.
+You may break some packages that were built against those packages, but once you
+have installed dev-db/postgresql-base and/or dev-db/postgresql-server you can
+run <c>revdep-rebuild</c> to reemerge any packages that may have been broken.
</p>
</body>
@@ -831,7 +835,7 @@ command:
</p>
<pre caption="Command to Add Instrumentation Functions">
-# <i>psql -U postgres --file /usr/share/postgresql-8.4/contrib/adminpack.sql</i>
+# <i>psql -U postgres --file /usr/share/postgresql-9.0/contrib/adminpack.sql</i>
</pre>
</body>
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [gentoo-commits] proj/pgsql-patches:documentation commit in: /
@ 2011-04-14 11:52 Aaron Swenson
0 siblings, 0 replies; 11+ messages in thread
From: Aaron Swenson @ 2011-04-14 11:52 UTC (permalink / raw
To: gentoo-commits
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=proj/pgsql-patches.git;a=commit;h=2875b515
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/>
-<version>7</version>
+<version>8</version>
<date>2011-03-28</date>
<chapter>
@@ -72,15 +72,8 @@ commands in this article as necessary for your specific version.
</p>
<impo>
-The 7.4 and 8.0 branch of PostgreSQL had their support dropped in October 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="#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 2011. Start
+planning your migration now.
</impo>
</body>
@@ -97,15 +90,16 @@ the same time. This is useful in such circumstances where you need to move data
from an older database to a new database, or need to have a production and a
testing database on the same machine. Also, this prevents a database,
corresponding libraries or executables from being overwritten by an incompatible
-update.
+update. That would require migration which is described in this guide.
</p>
<p>
Additionally, bug and security fixes, which are delivered via minor version
-updates, can be applied without fear of corrupting data; 9.0.2 can be updated to
-9.0.3 as they are guaranteed to be compatible and require no more interaction
-from you than to emerge it and restart the server process — neither
-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 are
+guaranteed to be compatible and require no more interaction from you than to
+emerge it and restart the server process — neither migration,
+reconfiguration nor initialization are necessary.
</p>
<p>
@@ -120,11 +114,11 @@ Versioning Policy</uri> for more information.
<body>
<p>
-There is quite a bit that will not be covered. If the <uri
-link="http://www.postgresql.org/docs/">official documentation</uri> were to be
-printed out on 8½x11 paper, it would be somewhere in the neighborhood 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 guidelines.
+There is quite a bit that will not be covered. The <uri
+link="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 out in
+this quick start guide. Only Gentoo specific issues will be covered and some
+basic configuration guidelines.
</p>
</body>
@@ -139,8 +133,9 @@ Gentoo specific issues will be covered and some basic configuration guidelines.
<p>
If you have any of the following ebuilds installed, then you have an older,
-obsolete Gentoo installation of PostgreSQL: dev-db/postgresql-libs,
-dev-db/postgresql-client, dev-db/libpq and/or dev-db/postgresql.
+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>
<p>
@@ -452,29 +447,21 @@ This time the focus is upon the files in the <e>PGDATA</e> directory,
<p>
This is the main configuration file. The line that you may find of immediate
interest is <e>listen_addresses</e>. This variable defines to which addresses
-PostgreSQL will bind. By default, only loopback devices and Unix sockets are
-bound; localhost and <path>/var/run/postgresql/.s.PGSQL.5432</path>. Changing
-<e>listen_addresses</e> is not enough, though, to enable remote
-connections. There is another file that actually controls the connections, 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="http://www.postgresql.org/docs/current/static/runtime-config.html">official
documentation</uri> is fairly easy to understand and is exhaustive on all the
settings available. It would behoove you to read that in addition to what is
covered here as some things may change.
</p>
-</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 REPORTING
+AND LOGGING.
</p>
<p>
@@ -485,14 +472,14 @@ defaults in <path>postgresql.conf</path> are reasonable enough to get you going.
</body>
</section>
<section>
-<title>Controlling Access</title>
+<title>pg_hba.conf</title>
<body>
<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 exhaustive 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 the
+database server and which authentication method must be used to establish 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>
<pre caption="Default pg_hba.conf">
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [gentoo-commits] proj/pgsql-patches:documentation commit in: /
@ 2011-04-14 11:52 Aaron Swenson
0 siblings, 0 replies; 11+ messages in thread
From: Aaron Swenson @ 2011-04-14 11:52 UTC (permalink / raw
To: gentoo-commits
commit: e56d1cba7a747d9c2a3f9168d7f331c2402e55f7
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 3 15:58:49 2011 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Sun Apr 3 15:58:49 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/pgsql-patches.git;a=commit;h=e56d1cba
Don't really need to document the documentation branch.
---
README | 25 -------------------------
1 files changed, 0 insertions(+), 25 deletions(-)
diff --git a/README b/README
deleted file mode 100644
index 8ca9912..0000000
--- a/README
+++ /dev/null
@@ -1,25 +0,0 @@
-This repository is split into three primary branches.
-
-Patches
--------------------------------------------------------------------------------
-The 'patches' branch is further split to match the major versions
-versions (a.k.a., slots). Pay attention to the tags as the signify the highest
-version they work with.
-
-Those files are then manually rolled into a tarball and hosted at
-'http://d.g.o/~titanofold/'.
-
-$ tar cjf postgresql-${SLOT}-patches.tbz2 postgresql-${SLOT}-*patch
-$ scp postgresql-${SLOT}-patches.tbz2 dev.gentoo.org:public_html
-
-
-Init Scripts
--------------------------------------------------------------------------------
-The 'initscripts' branch contains the initscripts. These scripts have been
-written to condense the number of files that are necessary for maintenance.
-
-
-Eselect Module
--------------------------------------------------------------------------------
-The 'eselect' branch contains the actual script for library and binary
-management.
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [gentoo-commits] proj/pgsql-patches:documentation commit in: /
@ 2011-07-04 22:55 Aaron Swenson
0 siblings, 0 replies; 11+ messages in thread
From: Aaron Swenson @ 2011-07-04 22:55 UTC (permalink / raw
To: gentoo-commits
commit: 8c4e0857d0808c07f16bd2cc4452b254ef66ab46
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 15 19:46:26 2011 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Wed Jun 15 19:46:26 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/pgsql-patches.git;a=commit;h=8c4e0857
Cleaned up some. Removed section about Sandbox as the ebuild now depends on the
proper version of Sandbox.
---
postgresql.xml | 123 +++++++++++++++++++++++---------------------------------
1 files changed, 51 insertions(+), 72 deletions(-)
diff --git a/postgresql.xml b/postgresql.xml
index c7bac14..174a384 100644
--- a/postgresql.xml
+++ b/postgresql.xml
@@ -158,9 +158,8 @@ ebuilds to the new ones.
<tr>
<ti>doc</ti>
<ti>
- Include the <uri
- link="http://www.postgresql.org/docs/">online documentation</uri> to be
- stored on your system
+ Include the <uri link="http://www.postgresql.org/docs/">online
+ documentation</uri> to be stored on your system
</ti>
</tr>
<tr>
@@ -195,15 +194,19 @@ ebuilds to the new ones.
<tr>
<ti>pg-intdatetime (Deprecated)</ti>
<ti>
- Use the newer method for formatting time stamps. Unless you had a previous
- installation that utilized the deprecated method, leave this enabled.
+ Use the newer, high resolution, 64-bit integer method for formatting
+ timestamps instead of the older, floating point method. Unless you had a
+ previous installation that utilized the deprecated method, leave this
+ enabled. (See note.)
</ti>
</tr>
<tr>
<ti>pg_legacytimestamp</ti>
<ti>
- Use the older method for formatting time stamps. Unless you had a previous
- installation that utilized the deprecated method, leave this disabled.
+ Use the older, floating-point method for formatting timestamps instead of
+ the higher resolution 64-bit integer method. Unless you had a previous
+ installation that utilized this deprecated method, leave this USE flag
+ disabled. (See note.)
</ti>
</tr>
<tr>
@@ -247,7 +250,7 @@ ebuilds to the new ones.
<ti>uuid</ti>
<ti>
Include support to generate a 128 bit random unique identifier. This is
- useful for merging databases together so the chances of collisions become
+ useful for merging databases together so the chances of collisions become
extremely low.
</ti>
</tr>
@@ -261,6 +264,12 @@ ebuilds to the new ones.
</tr>
</table>
+<note>
+Flipping the 'pg-intdatetime' or the 'pg_legacytimestamp' will required you to
+do a dump and restore if any of your databases utilize timestamps. The two
+methods are incompatible with each other.
+</note>
+
</body>
</section>
<section>
@@ -460,8 +469,8 @@ covered here as some things may change.
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, what and where to log. The section is marked: ERROR REPORTING
-AND LOGGING.
+options for how, what and where to log. The subsection is marked: ERROR
+REPORTING AND LOGGING.
</p>
<p>
@@ -506,9 +515,9 @@ database through the localhost. Even as the <e>postgres</e> database superuser.
<p>
To make a connection through the Unix socket, however, the users —
including the users for other services such as <e>apache</e> — must be in
-the <e>postgres</e> system group. Use <c>gpasswd -a <e>user</e> postgres</c>
-to add <e>user</e> to the <e>postgres</e> group. Users not in the
-<e>postgres</e> group will be rejected with "Permission denied".
+the <e>postgres</e> system group. Use <c>gpasswd -a <e>user</e> postgres</c> to
+add <e>user</e> to the <e>postgres</e> group. Users not in the <e>postgres</e>
+group will be rejected with "Permission denied".
</p>
<warn>
@@ -519,11 +528,11 @@ order to operate properly. The method can be changed freely.
<p>
The <e>trust</e> method is what allows any user to log on as any user without a
password. It specifies just what it implies: Trust all connections for the given
-type to the given database from the given database user (but not the system user)
-from the given location without a password. This is what allows any user on the
-system to log on as any user through the localhost connection from the get
-go. This is not as dangerous as it seems, but does pose a serious security risk
-in most circumstances.
+type to the given database from the given database user (but not the system
+user) from the given location without a password. This is what allows any user
+on the system to log on as any user through the localhost connection from the
+get go. This is not as dangerous as it seems, but does pose a serious security
+risk in most circumstances.
</p>
<p>
@@ -532,8 +541,8 @@ The two methods you will most likely use are: <e>password</e> and
start the connection and the password is sent "in-the-clear". This method is
fine when such information will never leave the machine, such as connecting via
the Unix socket or localhost. The md5 method is like password, but protects the
-password by using an md5 hash. This is what you want to use whenever the password
-is going to traverse a network.
+password by using an md5 hash. This is what you want to use whenever the
+password is going to traverse a network.
</p>
<p>
@@ -618,8 +627,8 @@ postgresql-9.0 | * Reloading PostgreSQL configuration ... [ ok ]
<p>
At this point you are ready to continue on with the official <uri
src="http://www.postgresql.org/docs/current/static/tutorial.html">PostgreSQL
-Tutorial</uri>. The tutorial will guide you through creating roles,
-databases, schemata and all that fun and useful stuff.
+Tutorial</uri>. The tutorial will guide you through creating roles, databases,
+schemata and all that fun and useful stuff.
</p>
</body>
@@ -627,15 +636,16 @@ databases, schemata and all that fun and useful stuff.
</chapter>
<chapter id="migrating">
-<title>Migrating from an Older Version of PostgreSQL</title>
+<title>Migrating PostgreSQL</title>
<section>
<title>When You Need to Migrate</title>
<body>
<p>
-You only need to perform a migration when moving from one major version to
-another, <e>e.g.</e>, from PostgreSQL 8.4.7 to 9.0.3, but not from 9.0.2 to
-9.0.3.
+There are only two reasons you would need to perform a migration: When moving
+from one major version to another, <e>e.g.</e>, from PostgreSQL 8.4.7 to 9.0.3,
+but not from 9.0.2 to 9.0.3; or when switching from the deprecated
+floating-point timestamp format to the new 64-bit integer timestamp format.
</p>
<note>
@@ -659,24 +669,27 @@ the migration process rather drastically.
<p>
However, there are two caveats with using pg_upgrade. Firstly, it does not
support configuration files being in a different directory than where the data
-is stored. This is resolved by using a symbolic link. Lastly, you can only use
-it to migrate from a database from 8.3 or newer. If you have an older database
-you will need to follow the "Pre-9.0 Migration" instructions.
+is stored. This is resolved by using symbolic links. Lastly, you can only use it
+to migrate from a database from 8.3 or newer. If you have an older database you
+will need to follow the "Pre-9.0 Migration" instructions.
</p>
<pre caption="Migrating with pg_upgrade">
-<comment>Stop the servers you're going to migrate from and to.</comment>
+<comment>(Stop the servers you're going to migrate from and to.)</comment>
# <i>/etc/init.d/postgresql-8.4 stop</i>
# <i>/etc/init.d/postgresql-9.0 stop</i>
# <i>ln -s /etc/postgresql-8.4/*.conf /var/lib/postgresql/8.4/data/</i>
# <i>ln -s /etc/postgresql-9.0/*.conf /var/lib/postgresql/9.0/data/</i>
-<comment>Change the method of 'postgres' to trust on local connections</comment>
+
+<comment>(Change the method of 'postgres' to trust on local connections)</comment>
# <i>nano -w /etc/postgresql-8.4/pg_hba.conf</i>
# <i>nano -w /etc/postgresql-9.0/pg_hba.conf</i>
-# <i>pg_upgrade -u postgres -d /var/lib/postgresql/8.4/data \
- -D /var/lib/postgresql/9.0 -b /usr/lib/postgresql-8.4/bin \
- -B /usr/lib/postgresql-9.0/bin</i>
-<comment>Perform the tasks pg_upgrade tells you to.</comment>
+# <i>pg_upgrade -u postgres \
+ -d /var/lib/postgresql/8.4/data -D /var/lib/postgresql/9.0 \
+ -b /usr/lib/postgresql-8.4/bin -B /usr/lib/postgresql-9.0/bin</i>
+<comment>(Perform the tasks pg_upgrade tells you to.)</comment>
+
+<comment>(Remove the symbolic links we created earlier.)</comment>
# <i>rm /var/lib/postgresql/8.4/data/*.conf</i>
# <i>rm /var/lib/postgresql/9.0/data/*.conf</i>
# <i>/etc/init.d/postgresql-9.0 start</i>
@@ -701,10 +714,10 @@ accordingly if you have deviated from the default.
</p>
<p>
-If you have not already done so, follow the <uri
+If you have not already done so, follow the <uri
link="#installation">installation instructions</uri> before starting the
-migration. Such a compile may hamper performance on the database server
-but it can keep going.
+migration. Such a compile may hamper performance on the database server but it
+can keep going.
</p>
<p>
@@ -827,39 +840,5 @@ command:
</body>
</section>
-<section>
-<title>Thread Safety Test Program Failed</title>
-<body>
-
-<p>
-If you get an error upon emerging dev-db/postgresql-base that reads as follows:
-</p>
-
-<pre caption="Thread Test Program Failed Error Message">
-# <i>emerge dev-db/postgresql-base</i>
-. . .
-configure: error: thread test program failed
-This platform is not thread-safe. Check the file 'config.log' for the
-exact reason.
-
-You can use the configure option --enable-thread-safety-force to force
-threads to be enabled. But you must then run the program in
-src/test/thread and add locking function calls to your applications to
-guarantee thread safety.
-</pre>
-
-<p>
-The solution, in most cases, is to update sandbox to a version greater than or
-equal to 2.0.
-</p>
-
-<pre caption="Emerge Newer Sandbox">
-# <i>echo '>=sys-apps/sandbox-2.0' >> /etc/portage/package.keywords</i>
-# <i>emerge -av '>=sys-apps/sandbox-2.0'</i>
-# <i>emerge -av dev-db/postgresql-base</i>
-</pre>
-
-</body>
-</section>
</chapter>
</guide>
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [gentoo-commits] proj/pgsql-patches:documentation commit in: /
@ 2011-07-13 11:26 Aaron Swenson
0 siblings, 0 replies; 11+ messages in thread
From: Aaron Swenson @ 2011-07-13 11:26 UTC (permalink / raw
To: gentoo-commits
commit: 4021386b67077b7ec4af269cf7046f7afb83cc73
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 13 11:26:05 2011 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Wed Jul 13 11:26:05 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/pgsql-patches.git;a=commit;h=4021386b
Changed the order of the migration subsection.
---
postgresql.xml | 88 ++++++++++++++++++++++++++++----------------------------
1 files changed, 44 insertions(+), 44 deletions(-)
diff --git a/postgresql.xml b/postgresql.xml
index 174a384..784789d 100644
--- a/postgresql.xml
+++ b/postgresql.xml
@@ -139,8 +139,7 @@ dev-db/postgresql.
</p>
<p>
-This article does cover <uri link="#migrating">migrating</uri> from an old
-database to a new one, and includes the steps needed for migrating from the old
+This article does cover <uri link="#oldmigration">migrating</uri> from the old
ebuilds to the new ones.
</p>
@@ -657,47 +656,7 @@ dev-db/postgresql-docs, dev-db/postgresql-base and dev-db/postgresql-server.
</body>
</section>
-<section id="Post90">
-<title>Post-9.0 Migration</title>
-<body>
-
-<p>
-<e>pg_upgrade</e>, a new utility that comes along with 9.0 and later, simplifies
-the migration process rather drastically.
-</p>
-
-<p>
-However, there are two caveats with using pg_upgrade. Firstly, it does not
-support configuration files being in a different directory than where the data
-is stored. This is resolved by using symbolic links. Lastly, you can only use it
-to migrate from a database from 8.3 or newer. If you have an older database you
-will need to follow the "Pre-9.0 Migration" instructions.
-</p>
-
-<pre caption="Migrating with pg_upgrade">
-<comment>(Stop the servers you're going to migrate from and to.)</comment>
-# <i>/etc/init.d/postgresql-8.4 stop</i>
-# <i>/etc/init.d/postgresql-9.0 stop</i>
-# <i>ln -s /etc/postgresql-8.4/*.conf /var/lib/postgresql/8.4/data/</i>
-# <i>ln -s /etc/postgresql-9.0/*.conf /var/lib/postgresql/9.0/data/</i>
-
-<comment>(Change the method of 'postgres' to trust on local connections)</comment>
-# <i>nano -w /etc/postgresql-8.4/pg_hba.conf</i>
-# <i>nano -w /etc/postgresql-9.0/pg_hba.conf</i>
-# <i>pg_upgrade -u postgres \
- -d /var/lib/postgresql/8.4/data -D /var/lib/postgresql/9.0 \
- -b /usr/lib/postgresql-8.4/bin -B /usr/lib/postgresql-9.0/bin</i>
-<comment>(Perform the tasks pg_upgrade tells you to.)</comment>
-
-<comment>(Remove the symbolic links we created earlier.)</comment>
-# <i>rm /var/lib/postgresql/8.4/data/*.conf</i>
-# <i>rm /var/lib/postgresql/9.0/data/*.conf</i>
-# <i>/etc/init.d/postgresql-9.0 start</i>
-</pre>
-
-</body>
-</section>
-<section>
+<section id="pre90">
<title>Pre-9.0 Migration: With the New Ebuilds</title>
<body>
@@ -765,7 +724,48 @@ server that contains precisely the same data, bit for bit, as the old server.
</body>
</section>
-<section>
+<section id="post90">
+<title>Post-9.0 Migration</title>
+<body>
+
+<p>
+<e>pg_upgrade</e>, a new utility that comes along with 9.0 and later, simplifies
+the migration process rather drastically.
+</p>
+
+<p>
+However, there are two caveats with using pg_upgrade. Firstly, it does not
+support configuration files being in a different directory than where the data
+is stored. This can be resolved by using symbolic links. Lastly, you can only
+use it to migrate from a database from 8.3 or newer. If you have an older
+database you will need to follow the <uri link="#pre90">Pre-9.0 Migration</uri>
+instructions.
+</p>
+
+<pre caption="Migrating with pg_upgrade">
+<comment>(Stop the servers you're going to migrate from and to.)</comment>
+# <i>/etc/init.d/postgresql-8.4 stop</i>
+# <i>/etc/init.d/postgresql-9.0 stop</i>
+# <i>ln -s /etc/postgresql-8.4/*.conf /var/lib/postgresql/8.4/data/</i>
+# <i>ln -s /etc/postgresql-9.0/*.conf /var/lib/postgresql/9.0/data/</i>
+
+<comment>(Change the method of 'postgres' to trust on local connections)</comment>
+# <i>nano -w /etc/postgresql-8.4/pg_hba.conf</i>
+# <i>nano -w /etc/postgresql-9.0/pg_hba.conf</i>
+# <i>pg_upgrade -u postgres \
+ -d /var/lib/postgresql/8.4/data -D /var/lib/postgresql/9.0 \
+ -b /usr/lib/postgresql-8.4/bin -B /usr/lib/postgresql-9.0/bin</i>
+<comment>(Perform the tasks pg_upgrade tells you to.)</comment>
+
+<comment>(Remove the symbolic links we created earlier.)</comment>
+# <i>rm /var/lib/postgresql/8.4/data/*.conf</i>
+# <i>rm /var/lib/postgresql/9.0/data/*.conf</i>
+# <i>/etc/init.d/postgresql-9.0 start</i>
+</pre>
+
+</body>
+</section>
+<section id="oldmigration">
<title>Pre-9.0 Migration: From the Obsolete Ebuilds</title>
<body>
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [gentoo-commits] proj/pgsql-patches:documentation commit in: /
@ 2011-07-23 15:38 Aaron Swenson
0 siblings, 0 replies; 11+ messages in thread
From: Aaron Swenson @ 2011-07-23 15:38 UTC (permalink / raw
To: gentoo-commits
commit: 88083a1b91957ff855bfa2f6eef2f8a7ef9357e9
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 23 15:38:09 2011 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Sat Jul 23 15:38:09 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/pgsql-patches.git;a=commit;h=88083a1b
Tabs to spaces. Updated my email address.
---
postgresql.xml | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/postgresql.xml b/postgresql.xml
index d07ca9a..5238f42 100644
--- a/postgresql.xml
+++ b/postgresql.xml
@@ -6,7 +6,7 @@
<title>PostgreSQL Quick Start Guide</title>
<author title="Author">
- <mail link="aaron.w.swenson@gmail.com">Aaron W. Swenson</mail>
+ <mail link="titanofold@gentoo.org">Aaron W. Swenson</mail>
</author>
<author title="Editor">
<mail link="pgsql-bugs@gentoo.org">Mikkel A. Clausen</mail>
@@ -362,10 +362,10 @@ following table lists the six options that, if used, are to be formatted as:
<ti>String sort order</ti>
</tr>
<tr>
- <ti>lc-ctype</ti>
- <ti>
- Character classification (What is a letter? Its upper-case equivalent?)
- </ti>
+ <ti>lc-ctype</ti>
+ <ti>
+ Character classification (What is a letter? Its upper-case equivalent?)
+ </ti>
</tr>
<tr>
<ti>lc-messages</ti>
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [gentoo-commits] proj/pgsql-patches:documentation commit in: /
@ 2011-07-23 15:38 Aaron Swenson
0 siblings, 0 replies; 11+ messages in thread
From: Aaron Swenson @ 2011-07-23 15:38 UTC (permalink / raw
To: gentoo-commits
commit: 1535baabb6f75bb0681884623b8c4932da3c81f2
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 21 23:05:45 2011 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Thu Jul 21 23:05:45 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/pgsql-patches.git;a=commit;h=1535baab
Revised
---
postgresql.xml | 96 ++++++++++++++++++++++++++++----------------------------
1 files changed, 48 insertions(+), 48 deletions(-)
diff --git a/postgresql.xml b/postgresql.xml
index 784789d..d07ca9a 100644
--- a/postgresql.xml
+++ b/postgresql.xml
@@ -264,9 +264,9 @@ ebuilds to the new ones.
</table>
<note>
-Flipping the 'pg-intdatetime' or the 'pg_legacytimestamp' will required you to
-do a dump and restore if any of your databases utilize timestamps. The two
-methods are incompatible with each other.
+Flipping the 'pg-intdatetime' or the 'pg_legacytimestamp' will require you to do
+a dump and restore if any of your databases utilize timestamps. The two methods
+are incompatible with each other.
</note>
</body>
@@ -292,7 +292,7 @@ You may receive a notice regarding that any of the above packages are blocked by
any or all of the following packages: dev-db/postgresql-libs,
dev-db/postgresql-client, dev-db/libpq or dev-db/postgresql. These packages are
<b>not maintained</b> and obsoleted. Refer to the section on <uri
-link="#migrating">migration</uri> for how to handle this situation.
+link="#oldmigration">migration</uri> for how to handle this situation.
</p>
</body>
@@ -336,8 +336,8 @@ PGDATA="/etc/postgresql-9.0/"
DATA_DIR="/var/lib/postgresql/9.0/data"
<comment># Additional options to pass to initdb.
-# See 'man initdb' for available options.
-#PG_INITDB_OPTS="--locale=en_US.UTF-8"</comment>
+# See 'man initdb' for available options.</comment>
+PG_INITDB_OPTS="--locale=en_US.UTF-8"
</pre>
<note>
@@ -427,7 +427,7 @@ To finish the installation:
<p>
This will create the database cluster and store all the related server files
-into <e>DATA_DIR</e>.
+into <e>PGDATA</e> and <e>DATA_DIR</e>.
</p>
</body>
@@ -656,6 +656,47 @@ dev-db/postgresql-docs, dev-db/postgresql-base and dev-db/postgresql-server.
</body>
</section>
+<section id="post90">
+<title>Post-9.0 Migration</title>
+<body>
+
+<p>
+<e>pg_upgrade</e>, a new utility that comes along with 9.0 and later, simplifies
+the migration process rather drastically.
+</p>
+
+<p>
+However, there are two caveats with using pg_upgrade. Firstly, it does not
+support configuration files being in a different directory than where the data
+is stored. This can be resolved by using symbolic links. Lastly, you can only
+use it to migrate from a database from 8.3 or newer. If you have an older
+database you will need to follow the <uri link="#pre90">Pre-9.0 Migration</uri>
+instructions.
+</p>
+
+<pre caption="Migrating with pg_upgrade">
+<comment>(Stop the servers you're going to migrate from and to.)</comment>
+# <i>/etc/init.d/postgresql-8.4 stop</i>
+# <i>/etc/init.d/postgresql-9.0 stop</i>
+# <i>ln -s /etc/postgresql-8.4/*.conf /var/lib/postgresql/8.4/data/</i>
+# <i>ln -s /etc/postgresql-9.0/*.conf /var/lib/postgresql/9.0/data/</i>
+
+<comment>(Change the method of 'postgres' to trust on local connections)</comment>
+# <i>nano -w /etc/postgresql-8.4/pg_hba.conf</i>
+# <i>nano -w /etc/postgresql-9.0/pg_hba.conf</i>
+# <i>pg_upgrade -u postgres \
+ -d /var/lib/postgresql/8.4/data -D /var/lib/postgresql/9.0 \
+ -b /usr/lib/postgresql-8.4/bin -B /usr/lib/postgresql-9.0/bin</i>
+<comment>(Perform the tasks pg_upgrade tells you to.)</comment>
+
+<comment>(Remove the symbolic links we created earlier.)</comment>
+# <i>rm /var/lib/postgresql/8.4/data/*.conf</i>
+# <i>rm /var/lib/postgresql/9.0/data/*.conf</i>
+# <i>/etc/init.d/postgresql-9.0 start</i>
+</pre>
+
+</body>
+</section>
<section id="pre90">
<title>Pre-9.0 Migration: With the New Ebuilds</title>
<body>
@@ -724,47 +765,6 @@ server that contains precisely the same data, bit for bit, as the old server.
</body>
</section>
-<section id="post90">
-<title>Post-9.0 Migration</title>
-<body>
-
-<p>
-<e>pg_upgrade</e>, a new utility that comes along with 9.0 and later, simplifies
-the migration process rather drastically.
-</p>
-
-<p>
-However, there are two caveats with using pg_upgrade. Firstly, it does not
-support configuration files being in a different directory than where the data
-is stored. This can be resolved by using symbolic links. Lastly, you can only
-use it to migrate from a database from 8.3 or newer. If you have an older
-database you will need to follow the <uri link="#pre90">Pre-9.0 Migration</uri>
-instructions.
-</p>
-
-<pre caption="Migrating with pg_upgrade">
-<comment>(Stop the servers you're going to migrate from and to.)</comment>
-# <i>/etc/init.d/postgresql-8.4 stop</i>
-# <i>/etc/init.d/postgresql-9.0 stop</i>
-# <i>ln -s /etc/postgresql-8.4/*.conf /var/lib/postgresql/8.4/data/</i>
-# <i>ln -s /etc/postgresql-9.0/*.conf /var/lib/postgresql/9.0/data/</i>
-
-<comment>(Change the method of 'postgres' to trust on local connections)</comment>
-# <i>nano -w /etc/postgresql-8.4/pg_hba.conf</i>
-# <i>nano -w /etc/postgresql-9.0/pg_hba.conf</i>
-# <i>pg_upgrade -u postgres \
- -d /var/lib/postgresql/8.4/data -D /var/lib/postgresql/9.0 \
- -b /usr/lib/postgresql-8.4/bin -B /usr/lib/postgresql-9.0/bin</i>
-<comment>(Perform the tasks pg_upgrade tells you to.)</comment>
-
-<comment>(Remove the symbolic links we created earlier.)</comment>
-# <i>rm /var/lib/postgresql/8.4/data/*.conf</i>
-# <i>rm /var/lib/postgresql/9.0/data/*.conf</i>
-# <i>/etc/init.d/postgresql-9.0 start</i>
-</pre>
-
-</body>
-</section>
<section id="oldmigration">
<title>Pre-9.0 Migration: From the Obsolete Ebuilds</title>
<body>
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [gentoo-commits] proj/pgsql-patches:documentation commit in: /
@ 2011-07-23 20:17 Aaron Swenson
0 siblings, 0 replies; 11+ messages in thread
From: Aaron Swenson @ 2011-07-23 20:17 UTC (permalink / raw
To: gentoo-commits
commit: 22e969f75462adc2e50f527b231d783aa5b551b3
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 23 20:16:32 2011 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Sat Jul 23 20:16:32 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/pgsql-patches.git;a=commit;h=22e969f7
Patched changes from David Abbott.
---
postgresql.xml | 21 +++++----------------
1 files changed, 5 insertions(+), 16 deletions(-)
diff --git a/postgresql.xml b/postgresql.xml
index 5238f42..ae1d8e5 100644
--- a/postgresql.xml
+++ b/postgresql.xml
@@ -404,21 +404,10 @@ in the documentation.
</p>
<p>
-You can change your locale and encoding selections at database creation time
-(<uri
-link="http://www.postgresql.org/docs/current/static/sql-createdatabase.html"><c>CREATE
-DATABASE</c></uri>). In order to change the locale for a database after you have
-created it, you must drop the database and start over again.
-</p>
-
-</body>
-</section>
-<section>
-<title>Initialize</title>
-<body>
-
-<p>
-To finish the installation:
+You can change your locale and encoding selections at database <uri
+ link="http://www.postgresql.org/docs/current/static/sql-createdatabase.html">creation
+ time.</uri> In order to change the locale for a database after you have
+created it, you must drop the database and start over again.
</p>
<pre caption="Finalize the installation">
@@ -625,7 +614,7 @@ postgresql-9.0 | * Reloading PostgreSQL configuration ... [ ok ]
<p>
At this point you are ready to continue on with the official <uri
-src="http://www.postgresql.org/docs/current/static/tutorial.html">PostgreSQL
+link="http://www.postgresql.org/docs/current/static/tutorial.html">PostgreSQL
Tutorial</uri>. The tutorial will guide you through creating roles, databases,
schemata and all that fun and useful stuff.
</p>
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [gentoo-commits] proj/pgsql-patches:documentation commit in: /
@ 2011-08-08 10:58 Aaron Swenson
0 siblings, 0 replies; 11+ messages in thread
From: Aaron Swenson @ 2011-08-08 10:58 UTC (permalink / raw
To: gentoo-commits
commit: 6a13c5d726fb9b5b38beb27776f15b879a4e1030
Author: Aaron W. Swenson <titanofold <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 8 10:57:59 2011 +0000
Commit: Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Mon Aug 8 10:57:59 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/pgsql-patches.git;a=commit;h=6a13c5d7
Fixed pg_upgrade instructions
---
postgresql.xml | 14 ++++++++++----
1 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/postgresql.xml b/postgresql.xml
index ae1d8e5..a612099 100644
--- a/postgresql.xml
+++ b/postgresql.xml
@@ -670,13 +670,19 @@ instructions.
# <i>ln -s /etc/postgresql-8.4/*.conf /var/lib/postgresql/8.4/data/</i>
# <i>ln -s /etc/postgresql-9.0/*.conf /var/lib/postgresql/9.0/data/</i>
-<comment>(Change the method of 'postgres' to trust on local connections)</comment>
+<comment>(Change the method of database user 'postgres' to trust on local
+connections on all databases.)</comment>
# <i>nano -w /etc/postgresql-8.4/pg_hba.conf</i>
# <i>nano -w /etc/postgresql-9.0/pg_hba.conf</i>
-# <i>pg_upgrade -u postgres \
- -d /var/lib/postgresql/8.4/data -D /var/lib/postgresql/9.0 \
+
+<comment>You may need to change the permissions of '/var/lib/postgresql/' before
+you perform the next step.</comment>
+# <i>su - postgres</i>
+$ <i>pg_upgrade -u postgres \
+ -d /var/lib/postgresql/8.4/data -D /var/lib/postgresql/9.0/data \
-b /usr/lib/postgresql-8.4/bin -B /usr/lib/postgresql-9.0/bin</i>
-<comment>(Perform the tasks pg_upgrade tells you to.)</comment>
+<comment>(Perform the tasks pg_upgrade tells you to do , if any.)</comment>
+$ <i>logout</i>
<comment>(Remove the symbolic links we created earlier.)</comment>
# <i>rm /var/lib/postgresql/8.4/data/*.conf</i>
^ permalink raw reply related [flat|nested] 11+ messages in thread
end of thread, other threads:[~2011-08-08 10:59 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-04 22:55 [gentoo-commits] proj/pgsql-patches:documentation commit in: / Aaron Swenson
-- strict thread matches above, loose matches on Subject: below --
2011-08-08 10:58 Aaron Swenson
2011-07-23 20:17 Aaron Swenson
2011-07-23 15:38 Aaron Swenson
2011-07-23 15:38 Aaron Swenson
2011-07-13 11:26 Aaron Swenson
2011-04-14 11:52 Aaron Swenson
2011-04-14 11:52 Aaron Swenson
2011-04-03 12:03 Aaron Swenson
2011-03-29 1:17 Aaron Swenson
2011-03-29 1:17 Aaron Swenson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox