Skip to content

Add support timescaledb #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Add support timescaledb #44

wants to merge 2 commits into from

Conversation

mnival
Copy link

@mnival mnival commented Feb 8, 2022

Hello,

Proposal of a solution for the support of timescaledb
Copy configuration from previous version to new version after initdb

@tianon
Copy link
Owner

tianon commented Feb 8, 2022

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" 🙈

@mnival
Copy link
Author

mnival commented Feb 8, 2022

Hello,

I understand and I just saw your comment in #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.

@mnival mnival closed this Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants