PostgreSQL (Русский)

From ArchWiki
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Эта статья описывает как настроить PostgreSQL и интегрировать ее с PHP и Apache. Она также описывает, как сделать PostgreSQL доступным из удаленного клиента. Считаем, что PHP и Apache уже установлены. Если вам нужна помощь настройки любой из этих программ, смотрите LAMP и следуйте всем разделам, кроме первого, связанного с MySQL.

Installing PostgreSQL

  • Install postgresql
$ sudo pacman -S postgresql
  • Start the PostgreSQL server (The first time that this is run it will create the data directory and users needed to run the server. As such you will see a lot of output.)
$ sudo /etc/rc.d/postgresql start
  • Check to make sure the postgres user is created and is in the postgres group.
$ groups postgres
  • (Optional) Add postgresql to the list of daemons that start on system startup in the /etc/rc.conf file

Creating Your First Database

  • Become the postgres user (This user was created when "/etc/rc.d/postgres start" was run)
su root
su - postgres
  • Add a new database user
createuser -DRSP <username>

-D User cannot create databases
-R User cannot create roles
-S User will not be a superuser
-P Prompt for password will be issued

Alternatively, you can use the createuser without parameter. Questions will be asked:

# createuser <username>
Shall the new role be a superuser? (y/n)  n
Shall the new role be allowed to create databases? (y/n)  y
Shall the new role be allowed to create more new roles? (y/n)  y

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 as (which makes it quite convenient).

  • Create a new database over which that user has read/write privileges
createdb -O username databasename [-E database_encoding]
  • That's It! Your database has been created.

Familiarizing Yourself with PostgreSQL

Access the database shell

  • Become the postgres user the first time, so we can assign permissions to you (your primary user)
$ sudo su postgres
  • Start the primary db shell, where you can do all your creation of databases/tables, deletion, set permissions, and run raw SQL commands.
$ psql
--You can optionally use `psql <database_name>` to administer an individual database.
  • Connect to a particular database
=> \c <database>
  • List all users and their permission levels
=> \du
  • Shows summary information about all tables in the current database
=> \dt

There are of course many more meta-commands, but these should help you get started.

Configure PostgreSQL to be accessible from remote

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 config files, including the pg_hba.conf.

Note: By default this folder will not even be browseable (or searchable) by a regular user, if you are wondering why `find` or `locate` isn't finding the conf files, this is the reason (threw me for a loop the first time I installed).
  1. As root user edit the file
    $ sudo vim /var/lib/postgres/data/postgresql.conf
  2. In the connections and authentications section uncomment or edit the listen_addresses line to your needs
    listen_addresses = '*'
    and take a careful look at the other lines.
  3. Hereafter insert the following line in the host-based authentication file /var/lib/postgres/data/pg_hba.conf. This file controls which hosts are allowed to connect, so be careful.
    # IPv4 local connections: <br>host   all   all   your_desired_ip_address/32   trust
    whereas your_desired_ip_address is the ip address of the client.
  4. After this you should restart the daemon process for the changes to take effect with
    $ sudo /etc/rc.d/postgresql restart
Note: Postgresql uses port 5432 by default for remote connections. So make sure this port is open and able to receive incoming connections

For troubleshooting take a look in the server log file

tail /var/log/postgresql.log

Configure PostgreSQL to Work With PHP

  1. Install the PHP-PostgreSQL modules
    $ pacman -S php-pgsql 
  2. Open the file /etc/php/php.ini with your editor of choice, e.g.,
    # vim /etc/php/php.ini
  3. Find the line that starts with, ";" and change it to, "". (Just remove the preceding ";"). If you need PDO, do the same thing with ";" and ";". If this lines are not present, add it. This lines may be in the "Dynamic Extensions" section of the file, or toward the very end of the file.
  4. Restart the Apache web server
    # /etc/rc.d/httpd restart

Change Default Encoding of New Databases To UTF-8 (Optional)

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 new database, one of the options is to change on-site template1. To do this, log into PostgresSQL shell (psql) and execute the following:

1. First, we need to drop template1. Templates can't be dropped, so we first modify it so it's an ordinary database:

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

2. Now we can drop it:

DROP DATABASE template1;

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


4. Now modify template1 so it's actually a template:

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

5. (RECOMMENDED) PostgreSQL documentation advises to VACUUM FREEZE the template:

\c template1

6. (OPTIONAL) If you don't want anyone connecting to this template, set datallowconn to FALSE:

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

Now you can create a new database by running from regular shell:

su - 
su - postgres
createdb blog;

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



                              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     |

Installing phpPgAdmin (optional)

phpPgAdmin is a web-based administration tool for PostgreSQL. It can be installed two ways.

Option A: install via Pacman (preferred)

  1. Make sure that the [community] repo is enabled.
  2. Install the package via Pacman
    # pacman -S phppgadmin

Option B: install via a manual install (the old way)

  1. Download the latest .bz2 file from here into the root of your server directory
    wget -P /home/httpd/html
  2. Extract the file into the new directory
    tar -C /home/httpd/html/ -jxvf /home/httpd/html/phpPgAdmin-4.1.3.tar.bz2
  3. Remove the tar file
    rm /home/httpd/html/phpPgAdmin-4.1.3.tar.bz2
  4. Change the name of the directory created in the previous step to include the version number (this will help in the future when upgrading)
    mv /home/httpd/html/phpPgAdmin /home/httpd/html/phpPgAdmin-4.1.3/
  5. Create a link to that directory (for ease of linking and upgrading)
    ln -s /home/httpd/html/phpPgAdmin-4.1.3/ /home/httpd/html/phpPgAdmin
  6. Copy the included generic config file
    cp /home/httpd/html/phpPgAdmin/conf/ /home/httpd/html/phpPgAdmin/conf/

The config file is located at /home/httpd/html/phpPgAdmin/conf/ No changes should be required. Check this page for any other setup questions that you might have.

Upgrading Postgresql

Warning: Official postgresql upgrade documentation should be followed.

First thing: these instructions could cause data loss. Use at your own risk. They work for me, but things change and nothing is guaranteed.

I would highly suggest adding the line

IgnorePkg = postgresql

to /etc/pacman.conf. This will make sure that you don't accidentally upgrade the database to an incompatible version. If you did an accidental upgrade you might not be able to access any of your data. Always check the Postgresql home page ( to be sure of what steps are required for each upgrade. For a bit about why this is the case see this.

How to dump all of your data, upgrade PostgreSQL, and then restore all of your data (this may not be necessary for every upgrade, see #2 above)

Become the root user


Become the postgres user

su postgres

Change the current directory to one that the postgres user can write to

eg. cd ~/data/

Dump the current contents of the database

pg_dumpall > pgs_db.out

Unless you have a .pgpass file setup, you will be required to enter your password a few times (the number of times is roughly equal to the number of databases that you have + 2). One problem occurs if you don't have a password defined for the postgres user but you require local users to authenticate. In this case you will be asked to give a password that doesn't exist. To work around this problem, add a line to your pg_hba.conf file to trust the postgres user. You can remove this line after the upgrade is complete. So, the first line of the 'local' section of pg_hba.conf would look something like this:

local     all postgres                                trust

Log out of the postgres user and return to superuser


Stop the PostgreSQL server

/etc/rc.d/postgresql stop

Move Postgresql's data directory

mv /var/lib/postgres /var/lib/postgres_old

Upgrade postgresql

pacman -S postgresql

Start the PostgreSQL server (this will create all needed files and directories)

/etc/rc.d/postgresql start

Become the postgres user

su postgres

Change the current directory to the directory that you dumped the data out to (in step 4 above)

eg. cd /var/lib/postgres_old/data/

Restore the database

psql -e template1 -f pgs_db.out

More Resources