#DO NOT DISABLE
# If you change this first entry you will need to make sure that the
# database
# super user can access the database using some other method.
# Noninteractive
# access to all databases is required during automatic maintenance
# (autovacuum, daily cronjob, replication, and similar tasks).
#
# Database administrative login by UNIX sockets
local all postgres ident
# TYPE DATABASE USER CIDR-ADDRESS METHOD

# “local” is for Unix domain socket connections only
local all all md5
# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5

# Connections for all PCs on the subnet
#
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
host all all [ipaddress] [subnet mask] md5

Follow this step to install latest Postgres:
- go to “Synaptic Package Manager” then search “postgresql” only, then click Apply
- while you are on “Synaptic Package Manager” search “pgadmin3″ only, then click Apply

then follow the other steps:
-----------------------------------
Configuring postgresql in Ubuntu

Now we need to reset the password for the ‘postgres’ admin account for the server

sudo su postgres -c psql template1
template1=# ALTER USER postgres WITH PASSWORD ‘password’;
template1=# \q

That alters the password for within the database, now we need to do the same for the unix user ‘postgres’:

sudo passwd -d postgres

sudo su postgres -c passwd

Now enter the same password that you used previously.

from here on in we can use both pgAdmin and command-line access (as the postgres user) to run the database server. But before you jump into pgAdmin we should set-up the PostgreSQL admin pack that enables better logging and monitoring within pgAdmin. Run the following at the command-line

we need to open up the server so that we can access and use it remotely - unless you only want to access the database on the local machine. To do this, first, we need to edit the postgresql.conf file:

sudo gedit /etc/postgresql/8.2/main/postgresql.conf

Now, to edit a couple of lines in the ‘Connections and Authentication’ section

Change the line

#listen_addresses = ‘localhost’

to

listen_addresses = ‘*’

and also change the line

#password_encryption = on

to

password_encryption = on

Then save the file and close gedit.

Now for the final step, we must define who can access the server. This is all done using the pg_hba.conf file.

sudo gedit /etc/postgresql/8.2/main/pg_hba.conf

Comment out, or delete the current contents of the file, then add this text to the bottom of the file

DO NOT DISABLE!
# If you change this first entry you will need to make sure that the
# database
# super user can access the database using some other method.
# Noninteractive
# access to all databases is required during automatic maintenance
# (autovacuum, daily cronjob, replication, and similar tasks).
#
# Database administrative login by UNIX sockets
local all postgres ident sameuser
# TYPE DATABASE USER CIDR-ADDRESS METHOD

# “local” is for Unix domain socket connections only
local all all md5
# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5

# Connections for all PCs on the subnet
#
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
host all all [ip address] [subnet mask] md5

and in the last line, add in your subnet mask (i.e. 255.255.255.0) and the IP address of the machine that you would like to access your server (i.e. 138.250.192.115). However, if you would like to enable access to a range of IP addresses, just substitute the last number for a zero and all machines within that range will be allowed access (i.e. 138.250.192.0 would allow all machines with an IP address 138.250.192.x to use the database server).

That’s it, now all you have to do is restart the server

sudo /etc/init.d/postgresql-8.2 restart

That’s it you can start using postgresql in Ubuntu

$ sudo su postgres -c psql < /usr/share/postgresql/8.2/contrib/adminpack.sql

At the end of this post :

http://moojix.wordpress.com/2008/06/24/install-postgresql-82-under-ubuntu-with-adminpack/

Many thanks for the tutorial.

petrus@petrus-laptop:~$ sudo gedit /etc/postgresql/8.2/main/postgresql.conf

(gedit:8166): Gtk-WARNING **: cannot open display:

After coding, I had to stop and start the service to make this thing works,
Thanks once!
Best regards!

Take that back, was not in root dir.

OMR

I see why I get no restart when I run the following this is all I get:

# find /* -name postg*
/etc/postgresql/8.2/main/postgresql.conf

so system contains no control script in the “/etc/init.d” dir.

OMR

Followed this HOWTO and got the the restart part and get:

root@u-main-svr:/etc/postgresql/8.2/main# sudo /etc/init.d/postgresql-8.2 restart
* Restarting PostgreSQL 8.2 database server * Error: pid file is invalid, please manually kill the stale server process.
[fail]

Tried a stop and start instead but no luck

What do I need to do to get around this problem?

OMR

ERROR: syntax error at or near “template1?

This is because template1=# is the prompt you’re supposed to see, not part of the command. In fact you’re seeing the prompt postgres=#, indicating that you’re logged in to the database ‘postgres’ rather than ‘template1′ that you should be. That in turn is because the earlier command listed above: sudo su postgres -c psql template1 is wrong- it should read sudo su postgres -c “psql -d template1″, which will connect you to database ‘template1′ as needed.

The typographical `quotes’ around the password in the instructions are wrong too- you need to replace them with simple ‘quotes’ or you will get other errors.

That said, I have been using this to help me set up my own postgresql server and it has helped me. Is it strictly true that the unix password for the user ‘postgresql’ needs to match the database server’s password for the user of the same name? I think I have got away in the past without making them match.