| |
@@ -11,26 +11,26 @@
|
| |
However, this is not recommended.
|
| |
|
| |
....
|
| |
- $ sudo yum install postgresql-server postgresql-contrib
|
| |
+ sudo yum install postgresql-server postgresql-contrib
|
| |
....
|
| |
|
| |
Or with dnf in Fedora 22 and later versions:
|
| |
|
| |
....
|
| |
- $ sudo dnf install postgresql-server postgresql-contrib
|
| |
+ sudo dnf install postgresql-server postgresql-contrib
|
| |
....
|
| |
|
| |
The postgresql server is turned off and disabled by default. You can
|
| |
enable its start during the boot using following command:
|
| |
|
| |
....
|
| |
- $ sudo systemctl enable postgresql
|
| |
+ sudo systemctl enable postgresql
|
| |
....
|
| |
|
| |
You can start the postgresql server only when necessary as follows.
|
| |
|
| |
....
|
| |
- $ sudo systemctl start postgresql
|
| |
+ sudo systemctl start postgresql
|
| |
Job for postgresql.service failed. See 'systemctl status postgresql.service' and 'journalctl -xn' for details.
|
| |
....
|
| |
|
| |
@@ -38,7 +38,7 @@
|
| |
The error log describes the problem and its solution.
|
| |
|
| |
....
|
| |
- $ journalctl -xn
|
| |
+ journalctl -xn
|
| |
-- Logs begin at Mon 2013-11-04 14:38:33 CET, end at Thu 2013-11-14 11:45:56 CET. --
|
| |
Nov 14 11:45:34 mlich-lenovo.usersys.redhat.com sudo[2054]: jmlich : TTY=pts/2 ; PWD=/home/jmlich ; USER=root ; COMMAND=/bin/systemctl status postgresql
|
| |
Nov 14 11:45:37 mlich-lenovo.usersys.redhat.com sudo[2073]: jmlich : TTY=pts/2 ; PWD=/home/jmlich ; USER=root ; COMMAND=/bin/systemctl status postgresql
|
| |
@@ -68,13 +68,13 @@
|
| |
creates the configuration files postgresql.conf and pg_hba.conf
|
| |
|
| |
....
|
| |
- $ sudo postgresql-setup initdb
|
| |
+ sudo postgresql-setup initdb
|
| |
....
|
| |
|
| |
Or on Fedora 22 and later:
|
| |
|
| |
....
|
| |
- $ sudo postgresql-setup --initdb --unit postgresql
|
| |
+ sudo postgresql-setup --initdb --unit postgresql
|
| |
....
|
| |
|
| |
[[upgrade]]
|
| |
@@ -92,7 +92,7 @@
|
| |
`postgresql-upgrade`:
|
| |
|
| |
....
|
| |
- $ postgresql-setup upgrade
|
| |
+ postgresql-setup upgrade
|
| |
|
| |
Redirecting to /bin/systemctl stop postgresql.service
|
| |
Upgrading database: OK
|
| |
@@ -118,24 +118,6 @@
|
| |
You can also upgrade by dumping your database and loading it again. For
|
| |
more information, see the link:#link-upgrade[official documentation].
|
| |
|
| |
- [[tips-and-tricks]]
|
| |
- == Tips and tricks
|
| |
-
|
| |
- For database management, it is more user-friendly to use graphical tools such as
|
| |
- phpPgAdmin or pgadmin3
|
| |
-
|
| |
- ....
|
| |
- $ sudo yum install phpPgAdmin
|
| |
- $ sudo yum install pgadmin3
|
| |
- ....
|
| |
-
|
| |
- Or with dnf in Fedora 22 and later versions:
|
| |
-
|
| |
- ....
|
| |
- $ sudo dnf install phpPgAdmin
|
| |
- $ sudo dnf install pgadmin3
|
| |
- ....
|
| |
-
|
| |
[[firewall]]
|
| |
== Firewall
|
| |
|
| |
@@ -143,16 +125,16 @@
|
| |
`postgresql.conf`). In firewalld you can open it like this:
|
| |
|
| |
....
|
| |
- $ # make it last after reboot
|
| |
- $ firewall-cmd --permanent --add-port=5432/tcp
|
| |
- $ # change runtime configuration
|
| |
- $ firewall-cmd --add-port=5432/tcp
|
| |
+ # make it last after reboot
|
| |
+ firewall-cmd --permanent --add-port=5432/tcp
|
| |
+ # change runtime configuration
|
| |
+ firewall-cmd --add-port=5432/tcp
|
| |
....
|
| |
|
| |
In the case of iptables:
|
| |
|
| |
....
|
| |
- $ iptables -A INPUT -p tcp --dport 5432 -m state --state NEW,ESTABLISHED -j ACCEPT
|
| |
+ iptables -A INPUT -p tcp --dport 5432 -m state --state NEW,ESTABLISHED -j ACCEPT
|
| |
....
|
| |
|
| |
Bear in mind that you probably don't want to open your database server
|
| |
@@ -167,13 +149,13 @@
|
| |
new location:
|
| |
|
| |
....
|
| |
- $ semanage fcontext -a -t postgresql_db_t "/my/new/location(/.*)?"
|
| |
+ semanage fcontext -a -t postgresql_db_t "/my/new/location(/.*)?"
|
| |
....
|
| |
|
| |
If the default port doesn't work for you, you may need to map postgre's port type to your desired port:
|
| |
|
| |
....
|
| |
- $ semanage port -a -t postgresql_port_t -p tcp 5433
|
| |
+ semanage port -a -t postgresql_port_t -p tcp 5433
|
| |
....
|
| |
|
| |
If you install a webapp that wants to communicate with PostgreSQL via
|
| |
@@ -181,7 +163,7 @@
|
| |
host:
|
| |
|
| |
....
|
| |
- # setsebool -P httpd_can_network_connect_db on
|
| |
+ setsebool -P httpd_can_network_connect_db on
|
| |
....
|
| |
|
| |
[[user-creation-and-database-creation]]
|
| |
@@ -191,13 +173,13 @@
|
| |
First, you have to switch the user to interact with `postgres`:
|
| |
|
| |
....
|
| |
- # su - postgres
|
| |
+ su - postgres
|
| |
....
|
| |
|
| |
and then run postgre's interactive shell:
|
| |
|
| |
....
|
| |
- $ psql
|
| |
+ psql
|
| |
psql (9.3.2)
|
| |
Type "help" for help.
|
| |
|
| |
@@ -214,8 +196,8 @@
|
| |
You can do this from the system shell as well:
|
| |
|
| |
....
|
| |
- $ createuser lenny
|
| |
- $ createdb --owner=lenny carl
|
| |
+ createuser lenny
|
| |
+ createdb --owner=lenny carl
|
| |
....
|
| |
|
| |
It might be good idea to add password for the `postgres` user:
|
| |
What this change accomplishes: