Closed mnival closed 2 years ago
Sorry, I'm really confused -- why would it make sense to add explicit timescaledb support to this repository?
My intention for creating this repository was an example of one way to solve the "postgres upgrade in containers" problem, not necessary "the only way to solve" :see_no_evil:
Hello,
I understand and I just saw your comment in https://github.com/tianon/docker-postgres-upgrade/issues/33.
Maybe only this part : cp -p ${PGDATANEW}/*.conf ${PGDATANEW}/new_conf/ [ -e ${PGDATAOLD}/pg_hba.conf.conf ] && cp -p ${PGDATAOLD}/pg_hba.conf ${PGDATANEW}/ [ -e ${PGDATAOLD}/postgresql.conf ] && cp -p ${PGDATAOLD}/postgresql.conf ${PGDATANEW}/
I don't know if it's a good idea to restore the previous configuration in the new data.
I close this pull request.
Hello,
Proposal of a solution for the support of timescaledb Copy configuration from previous version to new version after initdb