From: | Volkan Unsal <spocksplanet(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Melvin Davidson <melvin6925(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: no pg_hba.conf entry for replication connection from host |
Date: | 2015-04-10 20:06:49 |
Message-ID: | CAMcqKm=p=VA4AEzGG47L1D8W8iOKoXy59_sBUyeksmDnkFiEPQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Adrian,
I see nowhere in your init-master.sh where Postgres is restarted.
Yes, you're right. The base image takes care of that –– the base image of
mdillon/postgis is postgres:9.3. See here, for instance:
https://github.com/docker-library/postgres/blob/master/9.3/docker-entrypoint.sh#L70
When the startup command –– CMD in Docker lingo –– is "postgres" it does a
bunch of initialization operations, and then runs the user procided scripts
in the /docker-entrypoint-initdb.d directory.
Then finally it starts up the postgres process with *gosu postgres "$@". * The
gosu is a wrapper that passes user commands to the end process, i.e.
postgres, and I'm not sure what $@ is but I think it's to give the user a
shell.
--
*Volkan Unsal*
*web and mobile development*
volkanunsal.com <http://bit.ly/1h1ebjy>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-04-10 20:28:46 | Re: no pg_hba.conf entry for replication connection from host |
Previous Message | Edson Richter | 2015-04-10 19:51:58 | Intermitent connection could corrupt slave database? |