From 3c02e8afe44fcf232c8a75054d929faa280a9a0f Mon Sep 17 00:00:00 2001 From: Docker Library Bot Date: Fri, 23 Mar 2018 20:08:42 +0000 Subject: [PATCH] Run update.sh --- postgres/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/postgres/README.md b/postgres/README.md index 0727d611b..a82d048e0 100644 --- a/postgres/README.md +++ b/postgres/README.md @@ -247,7 +247,7 @@ Since database initialization only happens on container startup, this allows us There are many ways to set PostgreSQL server configuration. For information on what is available to configure, see the postgresql.org [docs](https://www.postgresql.org/docs/current/static/runtime-config.html) for the specific version of PostgreSQL that you are running. Here are a few options for setting configuration: -- Use a custom config file. Create a config file and get it into the container. If you need a starting place for your config file you can use the sample provided by PostgreSQL which is available in the container at `/usr/share/postgresql/postgresql.conf.sample`. +- Use a custom config file. Create a config file and get it into the container. If you need a starting place for your config file you can use the sample provided by PostgreSQL which is available in the container at `/usr/share/postgresql/postgresql.conf.sample` (`/usr/local/share/postgresql/postgresql.conf.sample` in Alpine variants). - **Important note:** you must set `listen_addresses = '*'`so that other containers will be able to access postgres.