Use PostgreSQL Relational Databases on Fedora 14

Select distribution:
Traducciones al Español
Estamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Deprecated

This guide has been deprecated and is no longer being maintained.

Create a Linode account to try this guide with a $ credit.
This credit will be applied to any valid services used during your first  days.

The PostgreSQL relational database system is a fast, scalable, and standards-compliant open source database platform. This guide will help you install and configure PostgreSQL on Fedora 14. We assume you’ve followed the steps detailed in our Setting Up and Securing a Compute Instance, and that you’re logged into your Linode as root via SSH.

System Configuration

Make sure your /etc/hosts file has proper entries, similar to the ones shown below. Replace “12.34.56.78” with your Linode’s public address, “servername” with your short hostname, and “mydomain.com” with your system’s domain name.

File: /etc/hosts
1
127.0.0.1 localhost.localdomain localhost 12.34.56.78 servername.mydomain.com servername

Set your system’s hostname by issuing the following commands. Replace “servername” with your system’s short hostname.

echo "HOSTNAME=servername" >> /etc/sysconfig/network
hostname "servername"

Install PostgreSQL

Make sure your system is up to date by issuing the following command:

yum update

Issue the following command to install PostgreSQL and required dependencies:

yum install postgresql postgresql-server

The current version of the database server will be installed, along with several supporting packages. Start the database server with the following commands:

chkconfig postgresql on
/etc/init.d/postgresql initdb
service postgresql start

Configure PostgreSQL

Set the PostgreSQL Password

Set a password for the “postgres” user by issuing the following command (be sure to substitute your postgres password for “CHANGME” below):

passwd postgres
su - postgres
psql -d template1 -c "ALTER USER postgres WITH PASSWORD 'CHANGEME';"

You should pick a password consisting of numbers, letters, and non-alphanumeric characters. As with other account passwords, it should be a minimum of eight characters in length.

Create a Database

Create a database and connect to it with psql by issuing the following commands:

createdb mytestdb
psql mytestdb

You should see output similar to the following:

-bash-4.1$ psql mytestdb
psql (8.4.5)
Type "help" for help.

mytestdb=#

This is the PostgreSQL client shell; you may use it to issue SQL statements. To see a list of available commands, use the following command in the shell:

\h

To get help on a specific command enter it after \h, as shown below for the “SELECT” command:

\h SELECT

Create a Database Table

To create a table in your test database called “employees”, issue the following command:

CREATE TABLE employees (employee_id int, first_name varchar, last_name varchar);

To insert a record into the table, you would issue a statement like this:

INSERT INTO employees VALUES (1, 'Jack', 'Sprat');

To see the contents of the “employees” table, you would issue a SELECT statement similar to the following:

SELECT * FROM employees;

This would produce output similar to the following:

mytestdb=# SELECT * FROM employees;
 employee_id | first_name | last_name
-------------+------------+-----------
           1 | Jack       | Sprat
(1 row)

To exit the psql shell, issue this command:

\q

Create PostgreSQL Users (Roles)

PostgreSQL refers to users as “roles”, which may have different privileges on your databases. If a user is classified as a “superuser” it will have administrative access to the database system. To add a new user to PostgreSQL, issue the following command as the “postgres” user:

createuser alison --pwprompt

You will be asked to specify several values for the new user. To delete this user, issue the following command:

dropuser alison

By default, PostgreSQL uses ident authentication. This means database connections will be granted to local system users that own or have privileges on the database being connected to. Such authentication is useful in cases where a particular system user will be running a program (local scripts, CGI/FastCGI processes owned by separate users, etc). However, you may wish to change this behavior to require passwords. To do so, edit the file /var/lib/pgsql/data/pg_hba.conf as root or the postgres user. Find the following line:

File: /var/lib/pgsql/data/pg\_hba.conf
1
local all all ident

Change it to the following to use password authentication:

File: /var/lib/pgsql/data/pg\_hba.conf
1
local all all md5

As root, restart the PostgreSQL service:

service postgresql restart

Resume these instructions as the postgres user:

su - postgres

To grant all privileges on the table employees to a user named alison, issue the following commands:

psql mytestdb
GRANT ALL ON employees TO alison;
\q

To use the database mytestdb as alison, issue the following command:

psql -U alison -W mytestdb

You will be prompted to enter the password for the alison user and given psql shell access to the database.

Secure Remote Database Access

PostgreSQL listens for connections on localhost, and it is not advised to reconfigure it to listen on public IP addresses. If you would like to access your databases remotely using a graphical tool, please follow one of these guides:

More Information

You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.

This page was originally published on


Your Feedback Is Important

Let us know if this guide was helpful to you.


Join the conversation.
Read other comments or post your own below. Comments must be respectful, constructive, and relevant to the topic of the guide. Do not post external links or advertisements. Before posting, consider if your comment would be better addressed by contacting our Support team or asking on our Community Site.
The Disqus commenting system for Linode Docs requires the acceptance of Functional Cookies, which allow us to analyze site usage so we can measure and improve performance. To view and create comments for this article, please update your Cookie Preferences on this website and refresh this web page. Please note: You must have JavaScript enabled in your browser.