熟悉PostgreSQL

Access the database shell

Become the postgres user. Start the primary db 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)

配置 PostgreSQL 被远程访问

As root user edit the file /var/lib/postgres/data/postgresql.conf.
In the connections and authentications section uncomment or edit the listen_addresses line to your needs:

listen_addresses = '*'

Take a careful look at the other lines.
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:
host all all your_desired_ip_address/32 trust

where your_desired_ip_address is the IP address of the client.
After this you should restart the daemon process for the changes to take effect with:

# systemctl restart postgresql

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

Install the PHP-PostgreSQL modules php-pgsql.
Edit the file /etc/php/php.ini. Find the line that starts with:

;extension=pgsql.so

Change it to:

extension=pgsql.so

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:

systemctl restart httpd

Change default data dir (optional)

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 assign it to user postgres (you eventually have to become root):

Change default encoding of new databases to UTF-8 (optional)

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

cannot write to log file pg_upgrade_internal.log Failure, exitingMake sure you're 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".

LC_COLLATE error that says that old and new values are differentFigure 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 isn't running. If you still get the error then chances are these an old PID file you need to clear out.

ERROR: could not access file "$libdir/postgis-2.0": No such file or directory Retrieve postgis-2.0.so from postgis package for version postgresql 9.2 () and copy it to /opt/pgsql-9.2/lib (make sure the privileges are right)

For those wishing to use pg_upgrade, a 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

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.

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 (/var/lib/postgres/data/postgresql.conf). Beware of the caveats, however.

synchronous_commit = off

空闲时防止磁盘写入

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: