Difference between revisions of "PostgreSQL"

From ArchWiki
Jump to: navigation, search
m (Configure PostgreSQL to be accessible from remote hosts: italicized)
 
(125 intermediate revisions by 65 users not shown)
Line 1: Line 1:
 
[[Category:Database management systems]]
 
[[Category:Database management systems]]
[[Category:Web Server]]
+
[[Category:Web server]]
 
[[it:PostgreSQL]]
 
[[it:PostgreSQL]]
 +
[[ja:PostgreSQL]]
 
[[ru:PostgreSQL]]
 
[[ru:PostgreSQL]]
 
[[zh-CN:PostgreSQL]]
 
[[zh-CN:PostgreSQL]]
{{Poor writing|excessive use of lists, please use them only when there are items to list.}}
+
{{Related articles start}}
 +
{{Related|PhpPgAdmin}}
 +
{{Related articles end}}
 +
[http://www.postgresql.org/ PostgreSQL] is an open source, community driven, standard compliant object-relational database system.
  
PostgreSQL is an open source, community driven, standard compliant object-relational database system.
+
This document describes how to set up PostgreSQL. It also describes how to configure PostgreSQL to be accessible from a remote client. Among other applications, PostgreSQL can be substituted for MySQL as part of the [[LAMP]] web stack.
  
This document describes how to set up PostgreSQL. It also describes how to configure PostgreSQL to be accessible from a remote client. If you need help setting up the rest of a web stack, see the [[LAMP]] page and follow all of the sections except the one related to [[MySQL]].
+
== Installing PostgreSQL ==
  
==Before you start==
+
[[Install]] the {{Pkg|postgresql}} package. Then [[Users_and_groups#Other_examples_of_user_management|set a password]] for the newly created ''postgres'' user.
Several sections have instructions stating "become the postgres user". If sudo is installed, execute the following to get a shell as the postgres user:
+
sudo -i -u postgres
+
  
Otherwise su can be used:
+
Then, switch to the default PostgreSQL user ''postgres'' by executing the following command:
su root
+
*If you have {{Pkg|sudo}} and your username is in {{ic|sudoers}}:
su - postgres
+
:{{bc|$ sudo -i -u postgres}}
 +
*Otherwise:
 +
:{{bc|<nowiki>
 +
$ su
 +
# su - postgres
 +
</nowiki>}}
  
==Installing PostgreSQL==
+
{{Note|Commands that should be run as the postgres user are prefixed by {{ic|[postgres]$}} in this article.}}
Install {{Pkg|postgresql}}
+
# pacman -S postgresql
+
Configure the PGROOT
+
  
Edit the /etc/conf.d/postgresql configuration file. If you don't know what value to use, just uncomment the line starting with "PGROOT" (the default directory is /var/lib/postgres).
+
Before PostgreSQL can function correctly, the database cluster must be initialized:
  
Create the file tmpfiles.d for /run/postgresql:
+
  [postgres]$ initdb --locale $LANG -E UTF8 -D '/var/lib/postgres/data'
  # systemd-tmpfiles --create postgresql.conf
+
  
Create the data directory (acordingly  with the PGROOT variable set before in the config file)
+
Where:
# mkdir /var/lib/postgres/data
+
* the ''--locale'' is the one defined in the file {{ic|/etc/locale.conf}};
Set /var/lib/postgres/data ownership to user 'postgres'
+
* the ''-E'' is the default encoding of the database that will be created in the future;
# chown -c postgres:postgres /var/lib/postgres/data
+
* and ''-D'' is the default location where the database cluster must be stored.
As user 'postgres' start the database (see first paragraph of this document for instructions on how to become a postgres user):
+
 
$ initdb -D '/var/lib/postgres/data'
+
A bunch of lines should now appear on the screen with several ending by ''... ok'':
Start PostgreSQL
+
{{bc|
# systemctl start postgresql
+
The files belonging to this database system will be owned by user "postgres".
(Optional) Add PostgreSQL to the list of daemons that start on system startup
+
This user must also own the server process.
# systemctl enable postgresql
+
 
 +
The database cluster will be initialized with locale "en_GB.UTF-8".
 +
The default text search configuration will be set to "english".
 +
 
 +
Data page checksums are disabled.
 +
 
 +
fixing permissions on existing directory /var/lib/postgres/data ... ok
 +
creating subdirectories ... ok
 +
selecting default max_connections ... 100
 +
selecting default shared_buffers ... 128MB
 +
selecting dynamic shared memory implementation ... posix
 +
creating configuration files ... ok
 +
creating template1 database in /var/lib/postgres/data/base/1 ... ok
 +
initializing pg_authid ... ok
 +
[...]}}
 +
 
 +
If this is the kind of lines you see, then the process succeeded. In that case return to the regular user using {{ic|exit}}.
 +
 
 +
Then as root, [[start]] and enable {{ic|postgresql.service}}.
  
==Creating Your First Database/User==
+
{{Warning|If the database resides on a [[Btrfs]] file system, you should consider disabling [[Btrfs#Copy-On-Write_.28CoW.29|Copy-on-Write]] for the directory before creating any database. If the database resides on a [[ZFS]] file system, you should consult [[ZFS#Database]] before creating any database.}}
Become the postgres user. Add a new database-user using the [http://www.postgresql.org/docs/9.0/static/app-createuser.html createuser] command.
+
  
If you create a user as per your login user ($USER) it allows you to access the postgresql database shell without having to specify a user to login (which makes it quite convenient).
+
== Create your first database/user ==
  
e.g. to create a superuser
+
{{Tip|If you create a PostgreSQL user with the same name as your Linux username, it allows you to access the PostgreSQL database shell without having to specify a user to login (which makes it quite convenient).}}
  
{{hc|$ createuser -s -U postgres --interactive|
+
Become the postgres user. Add a new database user using the [http://www.postgresql.org/docs/current/static/app-createuser.html createuser] command:
Enter name of role to add: myUsualArchLoginName}}
+
  
Create a new database over which the above user has read/write privileges using the [http://www.postgresql.org/docs/9.0/static/app-createdb.html createdb] command.
+
[postgres]$ createuser --interactive
  
From your login shell ('''not''' the postrgres user's)
+
Create a new database over which the above user has read/write privileges using the [http://www.postgresql.org/docs/current/static/app-createdb.html createdb] command (execute this command from your login shell if the database user has the same name as your Linux user, otherwise add {{ic|-U ''database-username''}} to the following command):
  
 
  $ createdb myDatabaseName
 
  $ createdb myDatabaseName
  
==Familiarizing Yourself with PostgreSQL==
+
== Familiarize with PostgreSQL ==
  
===Access the database shell===
+
=== Access the database shell ===
Become the postgres user. Start the primary db shell, [http://www.postgresql.org/docs/8.3/static/app-psql.html psql], where you can do all your creation of databases/tables, deletion, set permissions, and run raw SQL commands. Use the "-d" option to connect to the database you created (without specifying a database, psql will try to access a database that matches your username)
+
 
  $ psql -d myDatabaseName
+
Become the postgres user. Start the primary database shell, [http://www.postgresql.org/docs/current/static/app-psql.html psql], where you can do all your creation of databases/tables, deletion, set permissions, and run raw SQL commands. Use the {{ic|-d}} option to connect to the database you created (without specifying a database, {{ic|psql}} will try to access a database that matches your username).
 +
 
 +
  [postgres]$ psql -d myDatabaseName
  
 
Some helpful commands:
 
Some helpful commands:
  
Connect to a particular database
+
Get help:
 +
=> \help
 +
Connect to a particular database:
 
  => \c <database>
 
  => \c <database>
List all users and their permission levels
+
List all users and their permission levels:
 
  => \du
 
  => \du
Shows summary information about all tables in the current database
+
Show summary information about all tables in the current database:
 
  => \dt
 
  => \dt
exit/quit the psql shell
+
Exit/quit the {{ic|psql}} shell:
 
  => \q or CTRL+d
 
  => \q or CTRL+d
  
There are of course many more meta-commands, but these should help you get started.
+
There are of course many more meta-commands, but these should help you get started. To see all meta-commands run:
 +
=> \?
  
==Configure PostgreSQL to be accessible from remote hosts==
+
== Optional configuration ==
The PostgreSQL database server configuration file is <code>postgresql.conf</code>. This file is located in the data directory of the server, typically <code>/var/lib/postgres/data</code>. This folder also houses the other main config files, including the <code>pg_hba.conf</code>.
+
  
{{Note | By default this folder will not even be browseable (or searchable) by a regular user, if you are wondering why `find` or `locate` is not finding the conf files, this is the reason (threw me for a loop the first time I installed).}}
+
=== Configure PostgreSQL to be accessible from remote hosts ===
 +
 
 +
The PostgreSQL database server configuration file is {{ic|postgresql.conf}}. This file is located in the data directory of the server, typically {{ic|/var/lib/postgres/data}}. This folder also houses the other main configuration files, including the {{ic|pg_hba.conf}}.
 +
 
 +
{{Note|By default, this folder will not be browsable or searchable by a regular user. This is why {{ic|find}} and {{ic|locate}} are not finding the configuration files.}}
 +
 
 +
Edit the file {{ic|/var/lib/postgres/data/postgresql.conf}}. In the connections and authentications section, add the {{ic|listen_addresses}} line to your needs:
 +
 
 +
listen_addresses = 'localhost,''my_local_ip_address'''
 +
#You can use '*' to listen on all local addresses
 +
Take a careful look at the other lines.
 +
 
 +
Host-based authentication is configured in {{ic|/var/lib/postgres/data/pg_hba.conf}}. This file controls which hosts are allowed to connect. Note that the defaults '''allow any local user to connect as any database user''', including the database superuser. Add a line like the following:
  
As root user edit the file<br><pre># vim /var/lib/postgres/data/postgresql.conf</pre>
 
In the connections and authentications section uncomment or edit the <code>listen_addresses</code> line to your needs<br><pre>listen_addresses = '*'</pre>and take a careful look at the other lines.
 
Hereafter insert the following line in the host-based authentication file <code>/var/lib/postgres/data/pg_hba.conf</code>. This file controls which hosts are allowed to connect, '''so be careful'''.
 
 
  # IPv4 local connections:
 
  # IPv4 local connections:
  host  all  all  your_desired_ip_address/32  trust
+
  host  all  all  ''my_remote_client_ip_address''/32  md5
where <code>your_desired_ip_address</code> is the IP address of the client.
+
After this you should restart the daemon process for the changes to take effect with<br><pre># systemctl restart postgresql</pre>
+
  
{{Note | Postgresql uses port 5432 by default for remote connections. So make sure this port is open and able to receive incoming connections}}
+
where {{ic|my_remote_client_ip_address}} is the IP address of the client.
  
For troubleshooting take a look in the server log file
+
See the documentation for [http://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html pg_hba.conf].
tail /var/log/postgresql.log
+
  
==Configure PostgreSQL to Work With PHP==
+
After this you should [[restart]] {{ic|postgresql.service}} for the changes to take effect.
Install the PHP-PostgreSQL modules<pre># pacman -S php-pgsql </pre>
+
Open the file '''<code>/etc/php/php.ini</code>''' with your editor of choice, e.g.,<pre># vim /etc/php/php.ini</pre>
+
Find the line that starts with, ";extension=pgsql.so" and change it to, "extension=pgsql.so". (Just remove the preceding ";"). If you need PDO, do the same thing with ";extension=pdo.so" and ";extension=pdo_pgsql.so". If these lines are not present, add them. These lines may be in the "Dynamic Extensions" section of the file, or toward the very end of the file.
+
Restart the Apache web server<pre># systemctl restart httpd</pre>
+
  
==Change Default Data Dir (Optional)==
+
{{Note|PostgreSQL uses port {{ic|5432}} by default for remote connections. Make sure this port is open and able to receive incoming connections.}}
The default directory where all your newly created databases will be stored is <code>/var/lib/postgres/data</code>. To change this, follow these steps:
+
  
Create the new directory and assign it to user <code>postgres</code> (you eventually have to become root):
+
For troubleshooting take a look in the server log file:
  mkdir -p ''/pathto/pgroot/data''
+
 
  chown -R postgres:postgres ''/pathto/pgroot''
+
$ journalctl -u postgresql
Become the postgres user(change to root, then postgres user), and initialize the new cluster:
+
 
  initdb -D ''/pathto/pgroot/data''
+
=== Configure PostgreSQL authenticate against PAM ===
Edit <code>/etc/conf.d/postgresql</code> and change the PGROOT variable(optionally PGLOG) to point to your new pgroot directory.
+
 
  #PGROOT="/var/lib/postgres/"
+
PostgreSQL offers a number of authentication methods. If you would like to allow users to authenticate with their system password, additional steps are necessary. First you need to enable [[PAM]] for the connection.
PGROOT="''/pathto/pgroot/''"
+
 
If using systemd, copy <code>/usr/lib/systemd/system/postgresql.service</code> to <code>/etc/systemd/system/postgresql.service</code> and change the default PGROOT path.
+
For example, the same configuration as above, but with PAM enabled:
  #Environment=PGROOT=/var/lib/postgres/
+
 
 +
# IPv4 local connections:
 +
host  all  all  ''my_remote_client_ip_address''/32  pam
 +
 
 +
The PostgreSQL server is however running without root privileges and will not be able to access {{ic|/etc/shadow}}. We can work around that by allowing the postgres group to access this file:
 +
 
 +
setfacl -m g:postgres:r /etc/shadow
 +
 
 +
=== Change default data directory ===
 +
 
 +
The default directory where all your newly created databases will be stored is {{ic|/var/lib/postgres/data}}. To change this, follow these steps:
 +
 
 +
Create the new directory and make the postgres user its owner:
 +
 
 +
  # mkdir -p /pathto/pgroot/data
 +
  # chown -R postgres:postgres /pathto/pgroot
 +
 
 +
Become the postgres user, and initialize the new cluster:
 +
 
 +
  [postgres]$ initdb -D /pathto/pgroot/data
 +
 
 +
Some variables need to be overridden in the configuration, as described in [[Systemd#Editing provided units]]. First, run:
 +
  # systemctl edit postgresql.service
 +
 
 +
Systemctl will open a drop-in configuration file in your editor. Write the following in that file:
 +
 
 +
  [Service]
 
  Environment=PGROOT=''/pathto/pgroot/''
 
  Environment=PGROOT=''/pathto/pgroot/''
You will also need to change the default PIDFile path.
 
 
  PIDFile=''/pathto/pgroot/''data/postmaster.pid
 
  PIDFile=''/pathto/pgroot/''data/postmaster.pid
  
==Change Default Encoding of New Databases To UTF-8 (Optional)==
+
If you want to use {{ic|/home}} directory for default directory or for tablespaces, add one more line in this file:
When creating a new database (e.g. with <code>createdb blog</code>) PostgreSQL actually copies a template database. There are two predefined templates: template0 is vanilla, while template1 is meant as an on-site template changeable by the administrator and is used by default. In order to change the encoding of new database, one of the options is to change on-site template1. To do this, log into PostgresSQL shell (psql) and execute the following:
+
 
 +
ProtectHome=false
 +
 
 +
=== Change default encoding of new databases to UTF-8 ===
 +
 
 +
{{Note|If you ran {{ic|initdb}} with {{ic|-E UTF8}} these steps are not required.}}
 +
 
 +
When creating a new database (e.g. with {{ic|createdb blog}}) PostgreSQL actually copies a template database. There are two predefined templates: {{ic|template0}} is vanilla, while {{ic|template1}} is meant as an on-site template changeable by the administrator and is used by default. In order to change the encoding of a new database, one of the options is to change on-site {{ic|template1}}. To do this, log into PostgreSQL shell ({{ic|psql}}) and execute the following:
 +
 
 +
First, we need to drop {{ic|template1}}. Templates cannot be dropped, so we first modify it so it is an ordinary database:
  
First, we need to drop template1. Templates cannot be dropped, so we first modify it so it is an ordinary database:
 
 
  UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';
 
  UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';
 +
 
Now we can drop it:
 
Now we can drop it:
 +
 
  DROP DATABASE template1;
 
  DROP DATABASE template1;
The next step is to create a new database from template0, with a new default encoding:
+
 
 +
The next step is to create a new database from {{ic|template0}}, with a new default encoding:
 +
 
 
  CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE';
 
  CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE';
Now modify template1 so it is actually a template:
+
 
 +
Now modify {{ic|template1}} so it is actually a template:
 +
 
 
  UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1';
 
  UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1';
(OPTIONAL) If you do not want anyone connecting to this template, set datallowconn to FALSE:
+
 
 +
Optionally, if you do not want anyone connecting to this template, set {{ic|datallowconn}} to {{ic|FALSE}}:
 +
 
 
  UPDATE pg_database SET datallowconn = FALSE WHERE datname = 'template1';
 
  UPDATE pg_database SET datallowconn = FALSE WHERE datname = 'template1';
  
(this last step can create problems when upgrading via <code>pg_upgrade</code>)
+
{{Note|This last step can create problems when upgrading via {{ic|pg_upgrade}}.}}
  
Now you can create a new database by running from regular shell:
+
Now you can create a new database:
su -
+
 
  su - postgres
+
  [postgres]$ createdb blog
createdb blog;
+
 
 +
If you log back in to {{ic|psql}} and check the databases, you should see the proper encoding of your new database:
  
If you log in back to psql and check the databases, you should see the proper encoding of your new database:
 
 
  \l
 
  \l
 +
 
returns
 
returns
 
                               List of databases
 
                               List of databases
Line 148: Line 214:
 
  template1 | postgres | UTF8      | C        | C    |
 
  template1 | postgres | UTF8      | C        | C    |
  
==Installing phpPgAdmin (optional)==
+
== Administration tools ==
[[Phppgadmin]] ([http://phppgadmin.sourceforge.net website]) is a web-based administration tool for PostgreSQL.
+
  
#Make sure that the [community] repo is enabled.
+
* {{App|[[phpPgAdmin]]|Web-based administration tool for PostgreSQL.|http://phppgadmin.sourceforge.net|{{Pkg|phppgadmin}}}}
#Install the package via Pacman<pre># pacman -S phppgadmin</pre>
+
* {{App|pgAdmin|GUI-based administration tool for PostgreSQL.|http://www.pgadmin.org/|{{Pkg|pgadmin3}}}}
  
==Installing pgAdmin (optional)==
+
== Setup HHVM to work with PostgreSQL ==
[http://www.pgadmin.org/ pgAdmin] is a GUI-based administration tool for PostgreSQL.
+
{{Out of date|hhvm-pgsql fails to compile against HHVM 3.7.0, but upstream has not resolved the problem yet. See https://github.com/PocketRent/hhvm-pgsql/issues/82|section=Setting up HHVM}}
#Install the package via Pacman<pre># pacman -S pgadmin3</pre>
+
$ git clone https://github.com/PocketRent/hhvm-pgsql.git
 +
$ cd hhvm-pgsql
 +
If you do not use a nightly build, then run this command (verified on HHVM 3.6.1) to avoid compile errors:
 +
$ git checkout tags/3.6.0
 +
Then build the extension (if you do not need an improved support for Hack language, then remove -DHACK_FRIENDLY=ON):
 +
$ hphpize
 +
$ cmake -DHACK_FRIENDLY=ON .
 +
$ make
 +
Then copy the built extension:
 +
# cp pgsql.so /etc/hhvm/
 +
Add to /etc/hhvm/server.ini:
 +
<pre>extension_dir = /etc/hhvm
 +
hhvm.extensions[pgsql] = pgsql.so</pre>
  
==Upgrading PostgreSQL ==
+
== Upgrading PostgreSQL ==
  
=== Quick Guide ===
+
Upgrading minor PostgreSQL versions (i.e. {{ic|9.2, 9.3, 9.4, 9.5}}) requires some extra maintenance.
This is for upgrading from 9.1 to 9.2.
+
  
  sudo pacman -S --needed postgresql-old-upgrade
+
{{Tip|If you already migrated from 9.2 to 9.3 and you want to migrate from 9.3 to 9.4, change versions before executing commands. If {{ic|/var/lib/postgres/data-9.2}} already exists and you just copy-paste all commands, {{ic|pg_upgrade}} will complain about the wrong version of the database, because your version 9.3 database will be stored in {{ic|/var/lib/postgres/data-9.2/data/}}.}}
  sudo -u postgres mv /var/lib/postgres/data /var/lib/postgres/data-9.1
+
  sudo -u postgres mkdir /var/lib/postgres/data
+
  sudo -u postgres initdb -D /var/lib/postgres/data
+
  sudo -u postgres pg_upgrade \
+
    -b /opt/pgsql-9.1/bin/ \
+
    -B /usr/bin/ \
+
    -d /var/lib/postgres/data-9.1 \
+
    -D /var/lib/postgres/data
+
  
If the "pg_upgrade" step fails with:
+
=== Quick guide ===
* ''cannot write to log file pg_upgrade_internal.log<br /> Failure, exiting'' <br />Make sure you're in a directory that the "postgres" user has enough rights to write the log file to (<code>/tmp</code> for example). Or use "su - postgres" instead of "sudo -u postgres".
+
* ''LC_COLLATE error that says that old and new values are different''<br />Figure out what the old locale was, C or en_US.UTF-8 for example, and force it when calling initdb.
+
  sudo -u postgres LC_ALL=C initdb -D /var/lib/postgres/data
+
  
* ''There seems to be a postmaster servicing the old cluster.<br/>Please shutdown that postmaster and try again.''<br/>Make sure postgres isn't running. If you still get the error then chances are these an old PID file you need to clear out.
+
If you had custom settings in configuration files like {{ic|pg_hba.conf}} and {{ic|postgresql.conf}}, merge them into the new ones.
  > sudo -u postgres ls -l /var/lib/postgres/data-9.1
+
    total 88
+
    -rw------- 1 postgres postgres    4 Mar 25  2012 PG_VERSION
+
    drwx------ 8 postgres postgres  4096 Jul 17 00:36 base
+
    drwx------ 2 postgres postgres  4096 Jul 17 00:38 global
+
    drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_clog
+
    -rw------- 1 postgres postgres  4476 Mar 25  2012 pg_hba.conf
+
    -rw------- 1 postgres postgres  1636 Mar 25  2012 pg_ident.conf
+
    drwx------ 4 postgres postgres  4096 Mar 25  2012 pg_multixact
+
    drwx------ 2 postgres postgres  4096 Jul 17 00:05 pg_notify
+
    drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_serial
+
    drwx------ 2 postgres postgres  4096 Jul 17 00:53 pg_stat_tmp
+
    drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_subtrans
+
    drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_tblspc
+
    drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_twophase
+
    drwx------ 3 postgres postgres  4096 Mar 25  2012 pg_xlog
+
    -rw------- 1 postgres postgres 19169 Mar 25  2012 postgresql.conf
+
    -rw------- 1 postgres postgres    48 Jul 17 00:05 postmaster.opts
+
    -rw------- 1 postgres postgres    80 Jul 17 00:05 postmaster.pid  # <-- This is the problem
+
 
+
  > sudo -u postgres mv /var/lib/postgres/data-9.1/postmaster.pid /tmp
+
* ''ERROR: could not access file "$libdir/postgis-2.0": No such file or directory'' <br> Retrieve postgis-2.0.so from postgis package for version postgresql 9.1 () and copy it to /opt/pgsql-9.1/lib (make sure the privileges are right)
+
  
=== Detailed Instructions ===
+
{{hc
{{Warning|Official PostgreSQL [http://www.postgresql.org/docs/current/static/upgrading.html upgrade] documentation should be followed.}}
+
|upgrade_pg.sh
 +
|<nowiki>
 +
## Set the old version that we want to upgrade from.
 +
export FROM_VERSION=9.4
  
Note that these instructions could cause data loss. '''Use at your own risk'''.
+
pacman -S --needed postgresql-old-upgrade
 +
chown postgres:postgres /var/lib/postgres/
 +
su - postgres -c "mv /var/lib/postgres/data /var/lib/postgres/data-${FROM_VERSION}"
 +
su - postgres -c 'mkdir /var/lib/postgres/data'
 +
su - postgres -c "initdb --locale $LANG -E UTF8 -D /var/lib/postgres/data"
 +
su - postgres -c "pg_upgrade -b /opt/pgsql-${FROM_VERSION}/bin/ -B /usr/bin/ -d /var/lib/postgres/data-${FROM_VERSION} -D /var/lib/postgres/data"
 +
</nowiki>}}
 +
 
 +
==== Troubleshooting ====
 +
 
 +
If the {{ic|pg_upgrade}} step fails with the following messages,
 +
 
 +
; cannot write to log file pg_upgrade_internal.log
 +
; Failure, exiting
 +
 
 +
: Make sure you are in a directory that the postgres user has enough rights to write the log file to ({{ic|/tmp}} for example), or use {{ic|su - postgres}} instead of {{ic|sudo -u postgres}}.
 +
 
 +
: If you are in a directory that postgres user has enough rights to write the log file to however you still get this error then make sure {{ic|/var/lib/postgres}} is owned by postgres
 +
 
 +
; LC_COLLATE error that says that old and new values are different
 +
 
 +
: Figure out what the old locale was, {{ic|C}} or {{ic|en_US.UTF-8}} for example, and force it when calling {{ic|initdb}}.
 +
: {{bc|<nowiki>sudo -u postgres LC_ALL=C initdb -D /var/lib/postgres/data</nowiki>}}
 +
 
 +
; There seems to be a postmaster servicing the old cluster.
 +
; Please shutdown that postmaster and try again.
 +
 
 +
: Make sure postgres is not running. If you still get the error, then chances are there is an old PID file you need to clear out.
 +
 
 +
: Find the old pid in old pg data,
 +
: {{bc|<nowiki>
 +
  $ sudo -u postgres ls -l /var/lib/postgres/data-9.X
 +
  total 88
 +
  -rw------- 1 postgres postgres    4 Mar 25  2012 PG_VERSION
 +
  drwx------ 8 postgres postgres  4096 Jul 17 00:36 base
 +
  drwx------ 2 postgres postgres  4096 Jul 17 00:38 global
 +
  drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_clog
 +
  -rw------- 1 postgres postgres  4476 Mar 25  2012 pg_hba.conf
 +
  -rw------- 1 postgres postgres  1636 Mar 25  2012 pg_ident.conf
 +
  drwx------ 4 postgres postgres  4096 Mar 25  2012 pg_multixact
 +
  drwx------ 2 postgres postgres  4096 Jul 17 00:05 pg_notify
 +
  drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_serial
 +
  drwx------ 2 postgres postgres  4096 Jul 17 00:53 pg_stat_tmp
 +
  drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_subtrans
 +
  drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_tblspc
 +
  drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_twophase
 +
  drwx------ 3 postgres postgres  4096 Mar 25  2012 pg_xlog
 +
  -rw------- 1 postgres postgres 19169 Mar 25  2012 postgresql.conf
 +
  -rw------- 1 postgres postgres    48 Jul 17 00:05 postmaster.opts
 +
  -rw------- 1 postgres postgres    80 Jul 17 00:05 postmaster.pid  # <-- This is the problem
 +
</nowiki>}}
 +
 
 +
: Move the old pid to temporary directory,
 +
 
 +
: {{bc|<nowiki>
 +
$ sudo -u postgres mv /var/lib/postgres/data-9.X/postmaster.pid /tmp
 +
</nowiki>}}
 +
 
 +
; <nowiki>ERROR: could not access file "$libdir/postgis-2.0": No such file or directory</nowiki>
 +
 
 +
: Retrieve {{ic|postgis-2.0.so}} from {{Pkg|postgis}} for version postgresql 9.X () and copy it to {{ic|/opt/pgsql-9.X/lib}} and make sure the privileges are readable by postgres user.
 +
 
 +
 
 +
; Your installation references loadable libraries that are missing from the new installation.
 +
; You can add these libraries to the new installation, or remove the functions using them from the old installation.
 +
; A list of problem libraries is in the file:
 +
;    loadable_libraries.txt
 +
 
 +
; Could not load library "$libdir/pg_upgrade_support"
 +
; <nowiki>ERROR: could not access file "$libdir/pg_upgrade_support": No such file or directory</nowiki>
 +
 
 +
: It means you have leftovers from old failed pg_upgrade attempts that you never completed. So you'll need to start postgres with old data and
 +
: in each database execute {{ic|DROP SCHEMA IF EXISTS binary_upgrade CASCADE;}}
 +
 
 +
=== Detailed instructions ===
 +
 
 +
{{Note|Official PostgreSQL [http://www.postgresql.org/docs/current/static/upgrading.html upgrade documentation] should be followed.}}
 +
 
 +
{{Warning|The following instructions could cause data loss. '''Use at your own risk'''.}}
 +
 
 +
It is recommended to add the following to your {{ic|/etc/pacman.conf}} file:
  
It is recommended to add the following to your <code>/etc/pacman.conf</code> file:
 
 
  IgnorePkg = postgresql postgresql-libs
 
  IgnorePkg = postgresql postgresql-libs
This will ensure you do not accidentally upgrade the database to an incompatible version. When an upgrade is available, pacman will notify you that it is skipping the upgrade because of the entry in pacman.conf.  Minor version upgrades (e.g., 9.0.3 to 9.0.4) are safe to perform. However, if you do an accidental upgrade to a different major version (e.g., 9.0.X to 9.1.X), you might not be able to access any of your data. Always check the PostgreSQL home page (http://www.postgresql.org/) to be sure of what steps are required for each upgrade. For a bit about why this is the case see the [http://www.postgresql.org/support/versioning versioning policy].
+
 
 +
This will ensure you do not accidentally upgrade the database to an incompatible version. When an upgrade is available, pacman will notify you that it is skipping the upgrade because of the entry in {{ic|pacman.conf}}.  Minor version upgrades (e.g. 9.0.3 to 9.0.4) are safe to perform. However, if you do an accidental upgrade to a different major version (e.g. 9.0.x to 9.1.x), you might not be able to access any of your data. Always check the PostgreSQL home page (http://www.postgresql.org/) to be sure of what steps are required for each upgrade. For a bit about why this is the case, see the [http://www.postgresql.org/support/versioning versioning policy].
  
 
There are two main ways to upgrade your PostgreSQL database. Read the official documentation for details.
 
There are two main ways to upgrade your PostgreSQL database. Read the official documentation for details.
  
For those wishing to use <code>pg_upgrade</code>, a {{Pkg|postgresql-old-upgrade}} package is available in the repositories that will always run one major version behind the real PostgreSQL package. This can be installed side by side with the new version of PostgreSQL. When you are ready to perform the upgrade, you can do
+
For those wishing to use {{ic|pg_upgrade}}, a {{Pkg|postgresql-old-upgrade}} package is available in the [[official repositories]] that will always run one major version behind the real PostgreSQL package. This can be installed side-by-side with the new version of PostgreSQL.  
pacman -Syu postgresql postgresql-libs postgresql-old-upgrade
+
Note also that the data directory does not change from version to version, so before running pg_upgrade it is necessary to rename your existing data directory and migrate into a new directory. The new database must be initialized by starting the server, as described near the top of this page.  The server then needs to be stopped before running pg_upgrade.
+
  
  # rc.d stop postgresql
+
When you are ready, upgrade the following packages: {{Pkg|postgresql}}, {{Pkg|postgresql-libs}}, and {{Pkg|postgresql-old-upgrade}}. Note that the data directory does not change from version to version, so before running {{ic|pg_upgrade}}, it is necessary to rename your existing data directory and migrate into a new directory. The new database must be initialized, as described near the top of this page.
 +
 
 +
  # systemctl stop postgresql
 
  # su - postgres -c 'mv /var/lib/postgres/data /var/lib/postgres/olddata'
 
  # su - postgres -c 'mv /var/lib/postgres/data /var/lib/postgres/olddata'
  # rc.d start postgresql
+
  # su - postgres -c 'initdb --locale en_US.UTF-8 -E UTF8 -D /var/lib/postgres/data'
# rc.d stop postgresql
+
  
Reference the [http://www.postgresql.org/docs/current/static/pgupgrade.html upstream pg_upgrade documentation] for details.
+
The upgrade invocation will likely look something like the following. '''Do not run this command blindly without understanding what it does!''' Reference the [http://www.postgresql.org/docs/current/static/pgupgrade.html upstream pg_upgrade documentation] for details.
  
The upgrade invocation will likely look something like the following (run as the postgres user). '''Do not run this command blindly without understanding what it does!'''
+
# su - postgres -c 'pg_upgrade -d /var/lib/postgres/olddata/ -D /var/lib/postgres/data/ -b /opt/pgsql-9.4/bin/ -B /usr/bin/'
  
# su - postgres -c 'pg_upgrade -d /var/lib/postgres/olddata/ -D /var/lib/postgres/data/ -b /opt/pgsql-8.4/bin/ -B /usr/bin/'
+
==== Manual dump and reload ====
  
You could also do something like this (after the upgrade and install of postgresql-old-upgrade)
+
You could also do something like this (after the upgrade and install of {{Pkg|postgresql-old-upgrade}}).
  
  # rc.d stop postgresql
+
{{Note|Below are the commands for PostgreSQL 9.4. You can find similar commands in {{ic|/opt/}} for PostgreSQL 9.2.}}
  # /opt/pgsql-8.4/bin/pg_ctl -D /var/lib/postgres/olddata/ start
+
 
  # pg_dumpall >> old_backup.sql
+
  # systemctl stop postgresql
  # /opt/pgsql-8.4/bin/pg_ctl -D /var/lib/postgres/olddata/ stop
+
  # /opt/pgsql-9.4/bin/pg_ctl -D /var/lib/postgres/olddata/ start
  # rc.d start postgresql
+
  # /opt/pgsql-9.4/bin/pg_dumpall >> old_backup.sql
 +
  # /opt/pgsql-9.4/bin/pg_ctl -D /var/lib/postgres/olddata/ stop
 +
  # systemctl start postgresql
 
  # psql -f old_backup.sql postgres
 
  # psql -f old_backup.sql postgres
  
==Troubleshooting==
+
== Troubleshooting ==
 +
 
 +
=== Improve performance of small transactions ===
  
===Improve performance of small transactions===
+
If you are using PostgresSQL on a local machine for development and it seems slow, you could try turning [http://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT synchronous_commit off] in the configuration. Beware of the [http://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT caveats], however.
  
If you are using PostgresSQL on a local machine for development and it seems slow, you could try turning [http://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT synchronous_commit off] in the configuration (<code>/var/lib/postgres/data/postgresql.conf</code>). Beware of the [http://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT caveats], however.
+
{{hc|/var/lib/postgres/data/postgresql.conf|<nowiki>synchronous_commit = off</nowiki>}}
  
<pre>synchronous_commit = off</pre>
+
=== Prevent disk writes when idle ===
  
===Prevent disk writes when idle===
+
PostgreSQL periodically updates its internal "statistics" file. By default, this file is stored on disk, which prevents disks from spinning down on laptops and causes hard drive seek noise. It is simple and safe to relocate this file to a memory-only file system with the following configuration option:
  
PostgreSQL periodically updates its internal "statistics" file. By default, this file is stored on disk, which prevents disks spinning down on laptops and causes hard drive seek noise. It's simple and safe to relocate this file to a memory-only file system with the following configuration option:
+
{{hc|/var/lib/postgres/data/postgresql.conf|<nowiki>stats_temp_directory = '/run/postgresql'</nowiki>}}
  
<pre>stats_temp_directory = '/run/postgresql'</pre>
+
===  Cannot connect to database through pg_connect()  ===
  
==See also==
+
Install {{Pkg|php-pgsql}} and edit the {{ic|php.ini}} file uncommenting the lines {{ic|extension<nowiki>=</nowiki>pdo_pgsql.so}}  and {{ic|extension<nowiki>=</nowiki>pgsql.so}}, then restart {{ic|httpd}}.
*[http://www.postgresql.org/ Official PostgreSQL Homepage]
+

Latest revision as of 16:33, 14 September 2016

Related articles

PostgreSQL is an open source, community driven, standard compliant object-relational database system.

This document describes how to set up PostgreSQL. It also describes how to configure PostgreSQL to be accessible from a remote client. Among other applications, PostgreSQL can be substituted for MySQL as part of the LAMP web stack.

Installing PostgreSQL

Install the postgresql package. Then set a password for the newly created postgres user.

Then, switch to the default PostgreSQL user postgres by executing the following command:

  • If you have sudo and your username is in sudoers:
$ sudo -i -u postgres
  • Otherwise:
$ su
# su - postgres
Note: Commands that should be run as the postgres user are prefixed by [postgres]$ in this article.

Before PostgreSQL can function correctly, the database cluster must be initialized:

[postgres]$ initdb --locale $LANG -E UTF8 -D '/var/lib/postgres/data'

Where:

  • the --locale is the one defined in the file /etc/locale.conf;
  • the -E is the default encoding of the database that will be created in the future;
  • and -D is the default location where the database cluster must be stored.

A bunch of lines should now appear on the screen with several ending by ... ok:

The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_GB.UTF-8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgres/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
creating template1 database in /var/lib/postgres/data/base/1 ... ok
initializing pg_authid ... ok
[...]

If this is the kind of lines you see, then the process succeeded. In that case return to the regular user using exit.

Then as root, start and enable postgresql.service.

Warning: If the database resides on a Btrfs file system, you should consider disabling Copy-on-Write for the directory before creating any database. If the database resides on a ZFS file system, you should consult ZFS#Database before creating any database.

Create your first database/user

Tip: If you create a PostgreSQL user with the same name as your Linux username, it allows you to access the PostgreSQL database shell without having to specify a user to login (which makes it quite convenient).

Become the postgres user. Add a new database user using the createuser command:

[postgres]$ createuser --interactive

Create a new database over which the above user has read/write privileges using the createdb command (execute this command from your login shell if the database user has the same name as your Linux user, otherwise add -U database-username to the following command):

$ createdb myDatabaseName

Familiarize with PostgreSQL

Access the database shell

Become the postgres user. Start the primary database shell, psql, where you can do all your creation of databases/tables, deletion, set permissions, and run raw SQL commands. Use the -d option to connect to the database you created (without specifying a database, psql will try to access a database that matches your username).

[postgres]$ psql -d myDatabaseName

Some helpful commands:

Get help:

=> \help

Connect to a particular database:

=> \c <database>

List all users and their permission levels:

=> \du

Show summary information about all tables in the current database:

=> \dt

Exit/quit the psql shell:

=> \q or CTRL+d

There are of course many more meta-commands, but these should help you get started. To see all meta-commands run:

=> \?

Optional configuration

Configure PostgreSQL to be accessible from remote hosts

The PostgreSQL database server configuration file is postgresql.conf. This file is located in the data directory of the server, typically /var/lib/postgres/data. This folder also houses the other main configuration files, including the pg_hba.conf.

Note: By default, this folder will not be browsable or searchable by a regular user. This is why find and locate are not finding the configuration files.

Edit the file /var/lib/postgres/data/postgresql.conf. In the connections and authentications section, add the listen_addresses line to your needs:

listen_addresses = 'localhost,my_local_ip_address'
#You can use '*' to listen on all local addresses

Take a careful look at the other lines.

Host-based authentication is configured in /var/lib/postgres/data/pg_hba.conf. This file controls which hosts are allowed to connect. Note that the defaults allow any local user to connect as any database user, including the database superuser. Add a line like the following:

# IPv4 local connections:
host   all   all   my_remote_client_ip_address/32   md5

where my_remote_client_ip_address is the IP address of the client.

See the documentation for pg_hba.conf.

After this you should restart postgresql.service for the changes to take effect.

Note: PostgreSQL uses port 5432 by default for remote connections. Make sure this port is open and able to receive incoming connections.

For troubleshooting take a look in the server log file:

$ journalctl -u postgresql

Configure PostgreSQL authenticate against PAM

PostgreSQL offers a number of authentication methods. If you would like to allow users to authenticate with their system password, additional steps are necessary. First you need to enable PAM for the connection.

For example, the same configuration as above, but with PAM enabled:

# IPv4 local connections:
host   all   all   my_remote_client_ip_address/32   pam

The PostgreSQL server is however running without root privileges and will not be able to access /etc/shadow. We can work around that by allowing the postgres group to access this file:

setfacl -m g:postgres:r /etc/shadow

Change default data directory

The default directory where all your newly created databases will be stored is /var/lib/postgres/data. To change this, follow these steps:

Create the new directory and make the postgres user its owner:

# mkdir -p /pathto/pgroot/data
# chown -R postgres:postgres /pathto/pgroot

Become the postgres user, and initialize the new cluster:

[postgres]$ initdb -D /pathto/pgroot/data

Some variables need to be overridden in the configuration, as described in Systemd#Editing provided units. First, run:

# systemctl edit postgresql.service

Systemctl will open a drop-in configuration file in your editor. Write the following in that file:

[Service]
Environment=PGROOT=/pathto/pgroot/
PIDFile=/pathto/pgroot/data/postmaster.pid

If you want to use /home directory for default directory or for tablespaces, add one more line in this file:

ProtectHome=false

Change default encoding of new databases to UTF-8

Note: If you ran initdb with -E UTF8 these steps are not required.

When creating a new database (e.g. with createdb blog) PostgreSQL actually copies a template database. There are two predefined templates: template0 is vanilla, while template1 is meant as an on-site template changeable by the administrator and is used by default. In order to change the encoding of a new database, one of the options is to change on-site template1. To do this, log into PostgreSQL shell (psql) and execute the following:

First, we need to drop template1. Templates cannot be dropped, so we first modify it so it is an ordinary database:

UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';

Now we can drop it:

DROP DATABASE template1;

The next step is to create a new database from template0, with a new default encoding:

CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE';

Now modify template1 so it is actually a template:

UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1';

Optionally, if you do not want anyone connecting to this template, set datallowconn to FALSE:

UPDATE pg_database SET datallowconn = FALSE WHERE datname = 'template1';
Note: This last step can create problems when upgrading via pg_upgrade.

Now you can create a new database:

[postgres]$ createdb blog

If you log back in to psql and check the databases, you should see the proper encoding of your new database:

\l

returns

                              List of databases
  Name    |  Owner   | Encoding  | Collation | Ctype |   Access privileges
-----------+----------+-----------+-----------+-------+----------------------
blog      | postgres | UTF8      | C         | C     |
postgres  | postgres | SQL_ASCII | C         | C     |
template0 | postgres | SQL_ASCII | C         | C     | =c/postgres
                                                     : postgres=CTc/postgres
template1 | postgres | UTF8      | C         | C     |

Administration tools

  • phpPgAdmin — Web-based administration tool for PostgreSQL.
http://phppgadmin.sourceforge.net || phppgadmin
  • pgAdmin — GUI-based administration tool for PostgreSQL.
http://www.pgadmin.org/ || pgadmin3

Setup HHVM to work with PostgreSQL

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: hhvm-pgsql fails to compile against HHVM 3.7.0, but upstream has not resolved the problem yet. See https://github.com/PocketRent/hhvm-pgsql/issues/82 (Discuss in Talk:PostgreSQL#Setting up HHVM)
$ git clone https://github.com/PocketRent/hhvm-pgsql.git
$ cd hhvm-pgsql

If you do not use a nightly build, then run this command (verified on HHVM 3.6.1) to avoid compile errors:

$ git checkout tags/3.6.0

Then build the extension (if you do not need an improved support for Hack language, then remove -DHACK_FRIENDLY=ON):

$ hphpize
$ cmake -DHACK_FRIENDLY=ON .
$ make

Then copy the built extension:

# cp pgsql.so /etc/hhvm/

Add to /etc/hhvm/server.ini:

extension_dir = /etc/hhvm
hhvm.extensions[pgsql] = pgsql.so

Upgrading PostgreSQL

Upgrading minor PostgreSQL versions (i.e. 9.2, 9.3, 9.4, 9.5) requires some extra maintenance.

Tip: If you already migrated from 9.2 to 9.3 and you want to migrate from 9.3 to 9.4, change versions before executing commands. If /var/lib/postgres/data-9.2 already exists and you just copy-paste all commands, pg_upgrade will complain about the wrong version of the database, because your version 9.3 database will be stored in /var/lib/postgres/data-9.2/data/.

Quick guide

If you had custom settings in configuration files like pg_hba.conf and postgresql.conf, merge them into the new ones.

upgrade_pg.sh
## Set the old version that we want to upgrade from.
export FROM_VERSION=9.4

pacman -S --needed postgresql-old-upgrade
chown postgres:postgres /var/lib/postgres/
su - postgres -c "mv /var/lib/postgres/data /var/lib/postgres/data-${FROM_VERSION}"
su - postgres -c 'mkdir /var/lib/postgres/data'
su - postgres -c "initdb --locale $LANG -E UTF8 -D /var/lib/postgres/data"
su - postgres -c "pg_upgrade -b /opt/pgsql-${FROM_VERSION}/bin/ -B /usr/bin/ -d /var/lib/postgres/data-${FROM_VERSION} -D /var/lib/postgres/data"

Troubleshooting

If the pg_upgrade step fails with the following messages,

cannot write to log file pg_upgrade_internal.log
Failure, exiting
Make sure you are in a directory that the postgres user has enough rights to write the log file to (/tmp for example), or use su - postgres instead of sudo -u postgres.
If you are in a directory that postgres user has enough rights to write the log file to however you still get this error then make sure /var/lib/postgres is owned by postgres
LC_COLLATE error that says that old and new values are different
Figure out what the old locale was, C or en_US.UTF-8 for example, and force it when calling initdb.
sudo -u postgres LC_ALL=C initdb -D /var/lib/postgres/data
There seems to be a postmaster servicing the old cluster.
Please shutdown that postmaster and try again.
Make sure postgres is not running. If you still get the error, then chances are there is an old PID file you need to clear out.
Find the old pid in old pg data,
  $ sudo -u postgres ls -l /var/lib/postgres/data-9.X
  total 88
  -rw------- 1 postgres postgres     4 Mar 25  2012 PG_VERSION
  drwx------ 8 postgres postgres  4096 Jul 17 00:36 base
  drwx------ 2 postgres postgres  4096 Jul 17 00:38 global
  drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_clog
  -rw------- 1 postgres postgres  4476 Mar 25  2012 pg_hba.conf
  -rw------- 1 postgres postgres  1636 Mar 25  2012 pg_ident.conf
  drwx------ 4 postgres postgres  4096 Mar 25  2012 pg_multixact
  drwx------ 2 postgres postgres  4096 Jul 17 00:05 pg_notify
  drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_serial
  drwx------ 2 postgres postgres  4096 Jul 17 00:53 pg_stat_tmp
  drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_subtrans
  drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_tblspc
  drwx------ 2 postgres postgres  4096 Mar 25  2012 pg_twophase
  drwx------ 3 postgres postgres  4096 Mar 25  2012 pg_xlog
  -rw------- 1 postgres postgres 19169 Mar 25  2012 postgresql.conf
  -rw------- 1 postgres postgres    48 Jul 17 00:05 postmaster.opts
  -rw------- 1 postgres postgres    80 Jul 17 00:05 postmaster.pid   # <-- This is the problem
Move the old pid to temporary directory,
$ sudo -u postgres mv /var/lib/postgres/data-9.X/postmaster.pid /tmp
ERROR: could not access file "$libdir/postgis-2.0": No such file or directory
Retrieve postgis-2.0.so from postgis for version postgresql 9.X () and copy it to /opt/pgsql-9.X/lib and make sure the privileges are readable by postgres user.


Your installation references loadable libraries that are missing from the new installation.
You can add these libraries to the new installation, or remove the functions using them from the old installation.
A list of problem libraries is in the file
loadable_libraries.txt
Could not load library "$libdir/pg_upgrade_support"
ERROR: could not access file "$libdir/pg_upgrade_support": No such file or directory
It means you have leftovers from old failed pg_upgrade attempts that you never completed. So you'll need to start postgres with old data and
in each database execute DROP SCHEMA IF EXISTS binary_upgrade CASCADE;

Detailed instructions

Note: Official PostgreSQL upgrade documentation should be followed.
Warning: The following instructions could cause data loss. Use at your own risk.

It is recommended to add the following to your /etc/pacman.conf file:

IgnorePkg = postgresql postgresql-libs

This will ensure you do not accidentally upgrade the database to an incompatible version. When an upgrade is available, pacman will notify you that it is skipping the upgrade because of the entry in pacman.conf. Minor version upgrades (e.g. 9.0.3 to 9.0.4) are safe to perform. However, if you do an accidental upgrade to a different major version (e.g. 9.0.x to 9.1.x), you might not be able to access any of your data. Always check the PostgreSQL home page (http://www.postgresql.org/) to be sure of what steps are required for each upgrade. For a bit about why this is the case, see the versioning policy.

There are two main ways to upgrade your PostgreSQL database. Read the official documentation for details.

For those wishing to use pg_upgrade, a postgresql-old-upgrade package is available in the official repositories that will always run one major version behind the real PostgreSQL package. This can be installed side-by-side with the new version of PostgreSQL.

When you are ready, upgrade the following packages: postgresql, postgresql-libs, and postgresql-old-upgrade. Note that the data directory does not change from version to version, so before running pg_upgrade, it is necessary to rename your existing data directory and migrate into a new directory. The new database must be initialized, as described near the top of this page.

# systemctl stop postgresql
# su - postgres -c 'mv /var/lib/postgres/data /var/lib/postgres/olddata'
# su - postgres -c 'initdb --locale en_US.UTF-8 -E UTF8 -D /var/lib/postgres/data'

The upgrade invocation will likely look something like the following. Do not run this command blindly without understanding what it does! Reference the upstream pg_upgrade documentation for details.

# su - postgres -c 'pg_upgrade -d /var/lib/postgres/olddata/ -D /var/lib/postgres/data/ -b /opt/pgsql-9.4/bin/ -B /usr/bin/'

Manual dump and reload

You could also do something like this (after the upgrade and install of postgresql-old-upgrade).

Note: Below are the commands for PostgreSQL 9.4. You can find similar commands in /opt/ for PostgreSQL 9.2.
# systemctl stop postgresql
# /opt/pgsql-9.4/bin/pg_ctl -D /var/lib/postgres/olddata/ start
# /opt/pgsql-9.4/bin/pg_dumpall >> old_backup.sql
# /opt/pgsql-9.4/bin/pg_ctl -D /var/lib/postgres/olddata/ stop
# systemctl start postgresql
# psql -f old_backup.sql postgres

Troubleshooting

Improve performance of small transactions

If you are using PostgresSQL on a local machine for development and it seems slow, you could try turning synchronous_commit off in the configuration. Beware of the caveats, however.

/var/lib/postgres/data/postgresql.conf
synchronous_commit = off

Prevent disk writes when idle

PostgreSQL periodically updates its internal "statistics" file. By default, this file is stored on disk, which prevents disks from spinning down on laptops and causes hard drive seek noise. It is simple and safe to relocate this file to a memory-only file system with the following configuration option:

/var/lib/postgres/data/postgresql.conf
stats_temp_directory = '/run/postgresql'

Cannot connect to database through pg_connect()

Install php-pgsql and edit the php.ini file uncommenting the lines extension=pdo_pgsql.so and extension=pgsql.so, then restart httpd.