Documentation Database Servers Beat
|Line 1:||Line 1:|
Revision as of 01:44, 17 September 2011
Warning - Beat Converted
The contents of this beat have been converted to Publican and sent for translation. The official Fedora 22 documentation now contains the information that was on this page.
If you have changes or corrections please file a bug. Use the product Fedora Documentation, component release-notes.
For the official copy of this beat, refer to [Release Notes the Fedora 22 Documentation].
MySQL and PostgreSQL have been updated to use native systemd unit files for startup, in place of the SysV-style init scripts. This should eliminate various unfortunate problems that occurred in Fedora 15 due to systemd's rather poor handling of SysV scripts. Also, handling of cases where the database server is slow to start up is significantly better than it ever was in the SysV scripts, since in systemd there is no reason not to wait until the server is really ready.
The "service postgresql initdb" and "service postgresql upgrade" actions that were supported by the SysV init script cannot be provided by the systemd unit file. There is a new standalone script postgresql-setup that provides these functions. For example, to initialize a new postgresql database, do something like
sudo postgresql-setup initdb
If you need to run more than one postgresql server on the same machine, you can duplicate and modify the
postgresql.service file, as is customary with systemd services. (Remember that custom service files should go into
/lib/systemd/system/.) Notice that PGDATA and PGPORT settings for alternate servers must now be specified in the custom service files; there is no longer any use of files in
You can use postgresql-setup for an alternate server by adding the name of the new service file to the command, for instance
sudo postgresql-setup initdb myservice
postgresql-setup will then extract the PGDATA setting from that service file instead of