Skip to main content

PostgreSQL Setup - Configuration



My friend wanted to setup PostGreSQL with Replication. (Master / Slave Setup). So I agreed to help him out.
Since I have not done anything on PostgreSQL before, so though to document it as I go.
First in this blog post, I will just cover.




  • Setting up two virtual machines (MASTER / SLAVE).
  • Getting both the VMs to have postgreSQL 9.1 installed and configured.
Information about the VM Machines
Master : 172.16.167.130
Slave : 172.16.167.129
Now Lets Start.

First, Lets setup VMWare setup to.
Installing VMware Player on Ubuntu 11.10.
Install required packages build-essential and linux-headers
sudo apt-get install build-essential linux-headers-$(uname -r)

Download the latest VMware player and execute below command.
$ gksudo bash ~/Downloads/VMware-Player-3.1.4-385536.i386.bundle

This will bring up the installer interface and you can continue after that.
Note: this assumes the location of your Downloads folder is ~/Downloads.


Now lets install PostgreSQL 9.1 on Ubuntu 11.10 (MASTER / SLAVE)
Lets Install PostgreSQL 9.1
ahmed@ahmed-work-horse:~$ sudo apt-get install postgresql-9.1*
This will install all the required components


ahmed@ahmed-work-horse:~$ sudo apt-get install pgadmin3
This is required for admin console.

Once we have done installing lets configure the Server.
ahmed@ubuntu:~$ sudo vim /etc/postgresql/9.1/main/postgresql.conf

In the file change (# is commented)
#listen_addresses = 'localhost'

to this (uncomment) - for MASTER is '172.16.167.130' SLAVE is '172.16.167.129'
listen_addresses = '172.16.167.130'
or
listen_addresses = '<your_ip_address>'

Next Lets change the pg_hba.conf file.
ahmed@ubuntu:~$ sudo vim /etc/postgresql/9.1/main/pg_hba.conf

Add these as required lines in the IPv4 Section.
This will allow IP 172.16.167.129 to access 172.16.167.130 (on Master)
This will allow IP 172.16.167.130 to access 172.16.167.129 (on Slave)

# IPv4 local connections:
host  all     all     127.0.0.1/32       md5
host  all     all     172.16.167.129/32  md5
host  all     all     172.16.167.130/32  md5
Now lets check our connection.
ahmed@ubuntu:~$ pgadmin3 &

This will bring up the pgadmin interface.
Follow the images below to check connection.
21 58 04
See the full gallery on Posterous

Replication, I will add once I have completed that.(In Progress)
Labels:

Comments

Post a Comment

Popular posts from this blog

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server ...
1 comment
Read more

Installing Zabbix Version 2.4 Offline (Zabbix Server without Internet).

There might be situations where you have a remote/zabbix server which does not have internet connectivity, due to security or other reasons. So we create a custom repo on the remote/zabbix server so that we can install zabbix using rpms Here is how we are planning to do this. Download all the dependency rpms on a machine which has internet connection, using yum-downloadonly or repotrack . Transfer all the rpms to the remote server. Create a repo on the remote server. Update yum configuration. Install. NOTE: This method can be used to install any application, but here we have used zabbix as we had this requirement for a zabbix server. Download dependent rpms . On a machine which has internet connection install the package below. And download all the rpms . Make sure the system are similar (not required to be identical - At-least the OS should be of same version) mkdir /zabbix_rpms yum install yum-downloadonly Downloading all the rpms to location /zabbix_rpms/ ,...
1 comment
Read more

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa...
1 comment
Read more