This also updates the entrypoint to allow for docker run postgres --flag --flag --flag.

This makes it possible for folks who want to embed a custom config in a new image (or to modify the existing config) to just replace /usr/share/postgresql/postgresql.conf.sample instead of thinking about which version of PostgreSQL they're using (or reference PG_MAJOR, which isn't even available at the time of -v when starting a container).

LGTM

@tianon

Now, can you give me an example on how to replace postgresql.conf and pg_hba.conf configuration files,

I do something like:

docker run \
  -v /somewhere/postgres/data:/var/lib/postgresql/data \
  -v /somewhere/postgres/postgresql.conf:/etc/postgres/postgresql.conf:ro \
  -v /somewhere/postgres/pg_hba.conf:/etc/postgres/pg_hba.conf:ro  postgres:9.4

But postgres ignores them.

@omidraha see #134 (comment):

We have not yet added docs on overriding the config, 😞

If you are replacing the .example with something like -v /my/local/postgres.conf:/usr/share/postgresql/postgresql.conf.sample then you would need to make sure that your conf file has a listen_addresses='*'. (where as a previously undocumented feature, you could've mounted to /usr/share/postgresql/9.5/postgresql.conf.sample and the startup script would've rewritten your listen address line for you.)

Found this thread and the related thread that @bw-matthew started, but with much effort.

@tianon - I feel that this is a very common use case. Should we include this in the README or docs?

@omidraha How did you resolve it?