Skip to main content

centos7 install postgresql

Using stock CentOS repositories

Installing PostgreSQL on CentOS7 can be done two ways:
  • From the PostgreSQL repositories
  • From the official CentOS repositories
The later will be described in this document
Installation
[root@localhost ~]#yum install -y postgresql postgresql-server postgresql-libs postgresql-contrib 
Initialization
[root@localhost ~]# postgresql-setup initdb
Make sure it starts at boot
[root@localhost ~]# systemctl enable postgresql
Start the service
[root@localhost ~]# systemctl start postgresql
Switch to the service user
[root@localhost ~]# su - postgres
MAke sure you access locally
-bash-4.2$ psql
postgres=#
User and database creation
-bash-4.2$ createuser --interactive --pwprompt jira
-bash-4.2$ createdb --owner=jira jira
Switch to the Jira user
[root@localhost ~]# su - jira
[jira@localhost ~]$ psql --username=jira --password
psql (9.2.10)
Type "help" for help.
jira=#
If you want to access PostgreSQL without being "jira" user, you need to configure
[root@localhost ~]# nano -w /var/lib/pgsql/data/pg_hba.conf
And add
[...]
host   jira jira     127.0.0.1/32     md5
[...]


Comments

Popular posts from this blog

vmware net_device trans_start

VMWare Workstation 12 and Kernel 4.7 When recompiling vmware kernel modules on a kernel 4.7, I get this error:

/tmp/modconfig-xrrZGZ/vmnet-only/netif.c:468:7: error: ‘struct net_device’ has no member named ‘trans_start’; did you mean ‘mem_start’?     dev->trans_start = jiffies;
This seems to be an already encountered problem: http://rglinuxtech.com/?p=1746http://ferenc.homelinux.com/?p=356 I choosed to replace the line, instead of deleting it.

- dev->trans_start = jiffies; + netif_trans_update(dev); I also noted that I had to re-tar the modified sources instead of leaving them untared, because the compilation process only takes the archives. 
On precedent editions of these files, I just left the modified folders "vmnet-only/" and "vmmon-only/" expanded without the need to re-tar them.


Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme.
I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create.
Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard:
"Create with shared configuration" will allow me to select the project I want the new one to share configuration with.

The new created project will use the same configuration as the project I selectThere will be no creation of Workflow and Issue Scheme that I need to cleanup

This fea…

dockerfile multiline to file

Outputing a multiline string from Dockerfile
I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian.
But I also have a local mirror and would like to use it for packages installation.

Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file.

Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write.
Here you are:

RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 " >>…