You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, if possible, without reconnecting database during init process is preferable.
The following diff is my suggestion, but I am not sure whether the sessions are separated and original #290 issue will be solved by this.
--- a/initdb-postgis.sh+++ b/initdb-postgis.sh
"${psql[@]}" --dbname="$DB" <<-'EOSQL'
CREATE EXTENSION IF NOT EXISTS postgis;
CREATE EXTENSION IF NOT EXISTS postgis_topology;
- -- Reconnect to update pg_setting.resetval- -- See https://github.com/postgis/docker-postgis/issues/288- \c+EOSQL++ "${psql[@]}" --dbname="$DB" <<-'EOSQL'
CREATE EXTENSION IF NOT EXISTS fuzzystrmatch;
CREATE EXTENSION IF NOT EXISTS postgis_tiger_geocoder;
EOSQL
The text was updated successfully, but these errors were encountered:
From #290 and #292, reconnecting database during init process was introduced, but this makes a dependency service management harder in
docker-compose.yml
like the following redmine usecase, because redmine database migration process starts before reconnecting database and failed.https://github.com/gtt-project/docker-gtt/blob/feature/simplify-docker-settings/docker-compose.yml
docker-compose.yml
side workaround is possible by waiting for lastpostgis_tiger_geocoder
extension like as follows, but this is not handy.So, if possible, without reconnecting database during init process is preferable.
The following diff is my suggestion, but I am not sure whether the sessions are separated and original #290 issue will be solved by this.
The text was updated successfully, but these errors were encountered: