From ca479d90cf5bbc14e94e910b5af430538ed39418 Mon Sep 17 00:00:00 2001 From: Sameer Naik Date: Wed, 18 Nov 2015 19:48:25 +0530 Subject: [PATCH] release 9.4-8 --- README.md | 28 ++++++++++++++-------------- VERSION | 2 +- 2 files changed, 15 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index c6ea709..b5151bb 100644 --- a/README.md +++ b/README.md @@ -62,7 +62,7 @@ Automated builds of the image are available on [Dockerhub](https://hub.docker.co > **Note**: Builds are also available on [Quay.io](https://quay.io/repository/sameersbn/postgresql) ```bash -docker pull sameersbn/postgresql:9.4-7 +docker pull sameersbn/postgresql:9.4-8 ``` Alternately you can build the image yourself. @@ -78,7 +78,7 @@ docker build -t="$USER/postgresql" . Run the postgresql image ```bash -docker run --name postgresql -d sameersbn/postgresql:9.4-7 +docker run --name postgresql -d sameersbn/postgresql:9.4-8 ``` The simplest way to login to the postgresql container as the administrative `postgres` user is to use the `docker exec` command to attach a new process to the running container and connect to the postgresql server over the unix socket. @@ -102,7 +102,7 @@ The updated run command looks like this. ```bash docker run --name postgresql -d \ - -v /opt/postgresql/data:/var/lib/postgresql sameersbn/postgresql:9.4-7 + -v /opt/postgresql/data:/var/lib/postgresql sameersbn/postgresql:9.4-8 ``` This will make sure that the data stored in the database is not lost when the image is stopped and started again. @@ -116,7 +116,7 @@ To create a new user you should specify the `DB_USER` and `DB_PASS` variables. T ```bash docker run --name postgresql -d \ -e 'DB_USER=dbuser' -e 'DB_PASS=dbpass' \ - sameersbn/postgresql:9.4-7 + sameersbn/postgresql:9.4-8 ``` **NOTE** @@ -127,7 +127,7 @@ Similarly, you can also create a new database by specifying the database name in ```bash docker run --name postgresql -d \ - -e 'DB_NAME=dbname' sameersbn/postgresql:9.4-7 + -e 'DB_NAME=dbname' sameersbn/postgresql:9.4-8 ``` You may also specify a comma separated list of database names in the `DB_NAME` variable. The following command creates two new databases named *dbname1* and *dbname2* (p.s. this feature is only available in releases greater than 9.1-1). @@ -135,7 +135,7 @@ You may also specify a comma separated list of database names in the `DB_NAME` v ```bash docker run --name postgresql -d \ -e 'DB_NAME=dbname1,dbname2' \ - sameersbn/postgresql:9.4-7 + sameersbn/postgresql:9.4-8 ``` If the `DB_USER` and `DB_PASS` variables are also specified while creating the database, then the user is granted access to the database(s). @@ -145,7 +145,7 @@ For example, ```bash docker run --name postgresql -d \ -e 'DB_USER=dbuser' -e 'DB_PASS=dbpass' -e 'DB_NAME=dbname' \ - sameersbn/postgresql:9.4-7 + sameersbn/postgresql:9.4-8 ``` will create a user *dbuser* with the password *dbpass*. It will also create a database named *dbname* and the *dbuser* user will have full access to the *dbname* database. @@ -159,7 +159,7 @@ For example, ```bash docker run --name postgresql -d \ -e 'PSQL_TRUST_LOCALNET=true' \ - sameersbn/postgresql:9.4-7 + sameersbn/postgresql:9.4-8 ``` This has the effect of adding the following to the `pg_hba.conf` file: @@ -181,7 +181,7 @@ docker run --name='psql-master' -it --rm \ -e 'PSQL_MODE=master' -e 'PSQL_TRUST_LOCALNET=true' \ -e 'REPLICATION_USER=replicator' -e 'REPLICATION_PASS=replicatorpass' \ -e 'DB_NAME=dbname' -e 'DB_USER=dbuser' -e 'DB_PASS=dbpass' \ - sameersbn/postgresql:9.4-7 + sameersbn/postgresql:9.4-8 ``` Create a streaming replication instance @@ -192,7 +192,7 @@ docker run --name='psql-slave' -it --rm \ -e 'PSQL_MODE=slave' -e 'PSQL_TRUST_LOCALNET=true' \ -e 'REPLICATION_HOST=psql-master' -e 'REPLICATION_PORT=5432' \ -e 'REPLICATION_USER=replicator' -e 'REPLICATION_PASS=replicatorpass' \ - sameersbn/postgresql:9.4-7 + sameersbn/postgresql:9.4-8 ``` # Enable Unaccent (Search plain text with accent) @@ -204,7 +204,7 @@ By default unaccent is configure to `false` ```bash docker run --name postgresql -d \ -e 'DB_UNACCENT=true' \ - sameersbn/postgresql:9.4-7 + sameersbn/postgresql:9.4-8 ``` # Host UID / GID Mapping @@ -216,7 +216,7 @@ Also the container processes seem to be executed as the host's user/group `[what ```bash docker run --name=postgresql -it --rm [options] \ --env="USERMAP_UID=$(id -u postgres)" --env="USERMAP_GID=$(id -g postgres)" \ - sameersbn/postgresql:9.4-7 + sameersbn/postgresql:9.4-8 ``` @@ -233,13 +233,13 @@ docker stop postgresql - **Step 2**: Update the docker image. ```bash -docker pull sameersbn/postgresql:9.4-7 +docker pull sameersbn/postgresql:9.4-8 ``` - **Step 3**: Start the image ```bash -docker run --name postgresql -d [OPTIONS] sameersbn/postgresql:9.4-7 +docker run --name postgresql -d [OPTIONS] sameersbn/postgresql:9.4-8 ``` # Shell Access diff --git a/VERSION b/VERSION index eebcaf8..cda0649 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -9.4-7 +9.4-8