Attachment 264045 Details for Bug 330927 – Reviewed/updated PostgreSQL guide

Reviewed/updated PostgreSQL guide

postgresql.xml (text/plain), 24.95 KB, created by Sven Vermeulen on 2011-02-27 14:38:41 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Sven Vermeulen

Created: 2011-02-27 14:38:41 UTC

Size: 24.95 KB

patch

obsolete

><?xml version="1.0" encoding="UTF-8"?>
><!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
>
>
><guide link="/doc/en/postgresql.xml" lang="en">
><title>PostgreSQL Quick Start Guide</title>
>
><author title="Author">
>  <mail link="aaron.w.swenson@gmail.com">Aaron W. Swenson</mail>
></author>
><author title="Editor">
>  <mail link="pgsql-bugs@gentoo.org">Mikkel A. Clausen</mail>
></author>
>
>
><abstract>
>This is a quick start guide to PostgreSQL. It covers emerging PostgreSQL and
>configuring it. This is complementary to the official documentation, but does
>not supplant it.
></abstract>
>
>
>
><license/>
>
><version>7</version>
><date>2011-02-27</date>
>
><chapter>
><title>Introduction</title>
><section>
><title>A Little Bit About PostgreSQL</title>
><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, schemas 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>
></section>
><section>
><title>What This Article Will Cover</title>
><body>
>
><p>
>This article will guide you through the Gentoo specific steps to install the
>PostgreSQL RDBMS.
></p>
>
><p>
>The Ebuilds covered by this article are <uri
>link="http://packages.gentoo.org/package/dev-db/postgresql-docs">dev-db/postgresql-docs</uri>,
><uri
>link="http://packages.gentoo.org/package/dev-db/postgresql-base">dev-db/postgresql-base</uri>
>and <uri
>link="http://packages.gentoo.org/package/dev-db/postgresql-server">dev-db/postgresql-server</uri>.
></p>
>
><p>
>This article assumes that you will be installing the latest, stable version of
>PostgreSQL; at the time of writing, the version was 8.4.4. Adjust the
>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 June 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>
>
></body>
></section>
><section>
><title>About the Ebuilds</title>
><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. For instance, 8.3 and 8.4 can be installed 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; 8.4.2 can be updated to
>8.4.4 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 necessary.
></p>
>
><p>
>Read the <uri link="http://www.postgresql.org/support/versioning">PostgreSQL
>Versioning Policy</uri> for more information.
></p>
>
></body>
></section>
><section>
><title>What this Article Will Not Cover</title>
><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.
></p>
>
></body>
></section>
></chapter>
>
><chapter id="installation">
><title>Installation</title>
><section>
><title>The Obsolete Ebuilds</title>
><body>
>
><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. 
></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.
></p>
>
></body>
></section>
><section>
><title>USE Flags</title>
><body>
>
><table>
>  <tr>
>    <th>USE Flag</th>
>    <th>Meaning</th>
>  </tr>
>  <tr>
>    <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>
>  </tr>
>  <tr>
>    <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>
>  </tr>
>  <tr>
>    <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>
>  </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>
>  </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>
>  </tr>
>  <tr>
>    <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>
>  </tr>
>  <tr>
>    <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>
>  </tr>
>  <tr>
>    <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>
>  </tr>
>  <tr>
>    <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>
>  </tr>
>  <tr>
>    <ti>zlib</ti>
>    <ti>Support for compressed archives in pg_dump and pg_restore.</ti>
>  </tr>
></table>
>
></body>
></section>
><section>
><title>Start Emerging</title>
><body>
>
><pre caption="Emerging PostgreSQL server">
># <i>emerge -av dev-db/postgresql-server</i>
>
>[ebuild N ] dev-db/postgresql-docs-8.4.4 0 kB
>[ebuild N ]dev-db/postgresql-base-8.4.4-r2 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
>[ebuild N ] dev-db/postgresql-server-8.4.4-r1 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
></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 obsoleted. Refer to the section on <uri
>link="#migrating">migration</uri> for how to handle this situation.
></p>
>
></body>
></section>
><section>
><title>Preparing to Initialize the Database Cluster</title>
><body>
>
><p>
>Once the packages have finished emerging, you may want to edit
><path>/etc/conf.d/postgresql-8.4</path>. There are two lines that affect the
>defaults of the server and <b>cannot</b> be changed later without deleting the
>directory that contains the database cluster and reinitializing.
></p>
>
><p>
><e>PGDATA</e> defines where to place the database cluster and related
>files. <e>PG_INITDB_OPTS</e> may contain any <uri
>link="http://www.postgresql.org/docs/8.4/interactive/app-initdb.html">extra
>options</uri> you would care to set. The extra options are <b>not</b> required
>as the reasonable defaults are, ahem, reasonable.
></p>
>
><p>
>In the following example, <e>PGDATA</e> states that the database cluster should
>be installed to <path>/var/lib/postgresql/8.4/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">
># PostgreSQL's Database Directory
>PGDATA="/var/lib/postgresql/8.4/data"
>
># Options to pass to PostgreSQL's initdb.
>PG_INITDB_OPTS="--locale=en_US.UTF-8"
></pre>
>
><p>
>This only determines the default locale and character encoding. You can specify
>different locales and/or character encodings at the database or table level in
>the same database cluster.
></p>
>
><p>
>There are six locale options that can be set to override <e>--locale=</e>. The
>following table lists the six options that, if used, are to be formatted as:
><c>--option=lo_LO.ENCODING</c>.
></p>
>
><table>
>  <tr>
>    <th>Option</th>
>    <th>Effects</th>
>  </tr>
>  <tr>
>    <ti>lc-collate</ti>
>    <ti>String sort order</ti>
>  </tr>
>  <tr>
>    <ti>lc-ctype</ti>
>    <ti>
>      Character classification (What is a letter? What is its upper-case
>      equivalent?)
>    </ti>
>  </tr>
>  <tr>
>    <ti>lc-messages</ti>
>    <ti>Language of messages</ti>
>  </tr>
>  <tr>
>    <ti>lc-monetary</ti>
>    <ti>Formatting of currency amounts</ti>
>  </tr>
>  <tr>
>    <ti>lc-numeric</ti>
>    <ti>Formatting of numbers</ti>
>  </tr>
>  <tr>
>    <ti>lc-time</ti>
>    <ti>Formatting of dates and times</ti>
>  </tr>
></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:
></p>
>
><pre caption="Example">
>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
>link="http://www.postgresql.org/docs/8.4/interactive/multibyte.html#CHARSET-TABLE">encodings</uri>
>in the documentation.
></p>
>
><p>
>You can change your locale and encoding selections at database creation time
>(<c>CREATE DATABASE</c>). Also, you can change the locale used within a database
>after it has been created with the exception of <e>LC_COLLATE</e> and
><e>LC_CTYPE</e>. To change the locale for these two, you must drop the database
>and start over again. The same applies for the encoding; you must drop the
>database to change the encoding.
></p>
>
></body>
></section>
><section>
><title>Initialize</title>
><body>
>
><p>
>To finish the installation:
></p>
>
><pre caption="Finalize the installation">
># <i>emerge --config =dev-db/postgresql-server-8.4.4-r1</i>
></pre>
>
><p>
>This will create the database cluster and store all the related server files
>into <e>PGDATA</e>.
></p>
>
></body>
></section>
></chapter>
>
><chapter>
><title>Configuration</title>
><section>
><title>Where the Configuration Files are Located</title>
><body>
>
><p>
>This time the focus is upon the files in the <e>PGDATA</e> directory
><path>/var/lib/postgresql/8.4/data/</path> instead with primary focus
>on the <path>postgresql.conf</path> and <path>pg_hba.conf</path> files.
></p>
>
><note>
>Actually after the installation, <e>PGDATA</e> defines where to find
><path>postgresql.conf</path>, which in turn may define where to find the other
>configuration files and data directory. But, for simplicity's sake, you should
>keep all of the configuration files in the same directory as the default is to
>refer to <e>PGDATA</e> for the location of all configuration files.
></note>
>
></body>
></section>
><section>
><title>postgresql.conf</title>
><body>
>
><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
>link="http://www.postgresql.org/docs/">official documentation</uri> is fairly
>easy to understand and is exhaustive on all the settings available. We
>recommend you to read the online official documentation on this.
></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>PGDATA</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.
></p>
>
></body>
></section>
><section>
><title>Controlling Access</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.
></p>
>
><pre caption="Default pg_hba.conf">
><comment># TYPE  DATABASE    USER        CIDR-ADDRESS          METHOD
>
># "local" is for Unix domain socket connections only</comment>
>local   all         all                               trust
><comment># IPv4 local connections:</comment>
>host    all         all         127.0.0.1/32          trust
><comment># IPv6 local connections:</comment>
>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.
></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>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>
>Never disable the Unix socket entirely. The initscripts require access to it in
>order to operate properly.
></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 (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>
>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 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>
>At this point, we would like to bring your attention to the last two
>lines (or four lines including comments) of the configuration file. PostgreSQL has
>native support for IPv6 regardless of your desires for such
>support. Additionally, IPv4 addresses are automatically mapped to IPv6
>addresses, so 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.
></p>
>
><pre caption="Example /etc/hosts">
><comment># IPv4 and IPv6 localhost aliases</comment>
>127.0.0.1       localhost
>::1             localhost
></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,
>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.
></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.
></p>
>
></body>
></section>
></chapter>
>
><chapter>
><title>Starting the Server</title>
><section>
><title>Give It a Go!</title>
><body>
>
><p>
>Now start PostgreSQL and set the password for the database superuser
><e>postgres</e>. The commands are to be performed as 'root' in the following
>code listing:
></p>
>
><pre caption="Starting the Server">
><comment>(Change 'trust' to 'password' for the localhost connections.)</comment>
># <i>nano -w /var/lib/postgresql/8.4/data/pg_hba.conf</i>
># <i>/etc/init.d/postgresql-8.4 start</i>
>postgresql-8.4  | * Starting PostgreSQL ...                               [ ok ]
>
><comment>(Open a connection to the server and set the password.)</comment>
># <i>psql -U postgres</i>
>psql (8.4.4)
>Type "help" for help.
>
>postgres=# <i>\password</i>
>Enter new password:
>Enter it again:
>postgres=# <i>\q</i>
>
><comment>(Change 'trust' to 'password' for the local connection.)</comment>
># <i>nano -w /var/lib/postgresql/8.4/data/pg_hba.conf</i>
># <i>/etc/init.d/postgresql-8.4 reload</i>
>postgresql-8.4 | * Reloading PostgreSQL configuration ...                 [ ok ]
># <i>rc-update add postgresql-8.4 default</i>
> * service postgresql-8.4 added to runlevel default
></pre>
>
></body>
></section>
></chapter>
>
><chapter id="migrating">
><title>Migrating from an Older Version of 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, for instance from PostgreSQL 8.3.11 to 8.4.4, but not from
>8.4.2 to 8.4.4.
></p>
>
><note>
>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-docs, 
>dev-db/postgresql-base and dev-db/postgresql-server).
></note>
>
></body>
></section>
><section>
><title>With the New Ebuilds</title>
><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
>hours.
></p>
>
><p>
>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="#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 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>
>Next, edit <path>/var/lib/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">
># <i>cd /var/lib/postgresql/</i>
># <i>cp -p 8.3/data/pg_hba.conf 8.4/data/</i>
>
><comment>(The following should be safe. Read the documentation to be sure.)</comment>
># <i> cp -p 8.3/data/postgresql.conf 8.4/data/</i>
><comment>
>(Don't forget to copy over any other configuration files that you may need.)
></comment>
># <i>/etc/init.d/postgresql-8.3 reload</i>
># <i>/etc/init.d/postgresql-8.4 start</i>
>
><comment>(Begin piping the data from the old cluster to the new cluster.)</comment>
># <i>pg_dumpall -U postgres -p 5432 | psql -U postgres -d postgres -p 6543</i>
># <i>/etc/init.d/postgresql-8.3 stop</i>
># <i>/etc/init.d/postgresql-8.4 stop</i>
>
><comment>(Edit PGPORT back to 5432.)</comment>
># <i>nano -w /etc/conf.d/postgresql-8.4</i>
>
><comment>(Allow users access once more.)</comment>
># <i>nano -w /var/lib/postgresql/8.4/data/pg_hba.conf</i>
># <i>/etc/init.d/postgresql-8.4 start</i>
># <i>rc-update del postgresql-8.3 &amp;&amp; rc-update add postgresql-8.4 default</i>
></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.
></p>
>
></body>
></section>
><section>
><title>From the Obsolete Ebuilds</title>
><body>
>
><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.
></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.
></p>
>
><pre caption="Steps to Migrate from the Obsolete Ebuilds">
># <i>pg_dumpall -U postgres > backup_file</i>
># <i>/etc/init.d/postgresql stop</i>
># <i>emerge -C dev-db/postgresql dev-db/libpq dev-db/postgresql-client \
>  dev-db/postgresql-client</i>
><comment>
>(Follow the steps detailed in this article for installing and configuring the
>server.)
></comment>
># <i>/etc/init.d/postgresql-8.4 start</i>
># <i>psql -f backup_file postgres</i>
></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.
></p>
>
></body>
></section>
></chapter>
>
><chapter>
><title>Utilities</title>
><section>
><title>pgAdminIII</title>
><body>
>
><p>
><uri link="http://www.pgadmin.org/">pgAdmin III</uri> is a graphical utility
>for managing PostgreSQL.
></p>
>
></body>
></section>
></chapter>
>
><chapter>
><title>Troubleshooting</title>
><section>
><title>Server Lacks Instrumentation Functions</title>
><body>
>
><p>
>This problem is easy to solve. What is difficult about it is finding the
>answer. What is required is an import from a file that already exists on the
>storage drive: <path>adminpack.sql</path>. To resolve this issue, run this
>command:
></p>
>
><pre caption="Command to Add Instrumentation Functions">
># <i>psql -U postgres --file /usr/share/postgresql-8.4/contrib/adminpack.sql</i>
></pre>
>
></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>

Actions: View

Attachments on bug 330927: 241161 | 264045