ansible-role-postgresql
ansible-role-postgresql copied to clipboard
Custom data dir
Fixes bugs #158, #40, #124 allowing for a custom data directory
This is a rebased version of #160, and #179
This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark pull requests as stale.
Rather, unless something is breaking stability (e.g. a project I maintain won't install anymore, or breaks completely and CI blows up), or there's a major feature or missing component that I agree would be a no-brainer to have incorporated
I reckon this is a no-brainer.
This issue is no longer marked for closure.
@geerlingguy any chance of this being merged?
The biggest use case for this is we can put it onto a separate volume than root without having all of /var in a separate disk in AWS.
Not stale
On Jun 22, 2022, at 9:00 PM, stale[bot] @.***> wrote:
This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark pull requests as stale.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.
I've tested this and it works well just by setting this in the config/vars:
postgresql_data_dir: "/data/pgsql/{{ postgresql_version }}/data"
Much easier to move the data to another mounted volume
This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark pull requests as stale.
Still not stale :)
This issue is no longer marked for closure.
This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark pull requests as stale.
not stale :)
On Sat, Jun 17, 2023 at 6:57 PM stale[bot] @.***> wrote:
This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution!
Please read this blog post https://www.jeffgeerling.com/blog/2020/enabling-stale-issue-bot-on-my-github-repositories to see the reasons why I mark pull requests as stale.
— Reply to this email directly, view it on GitHub https://github.com/geerlingguy/ansible-role-postgresql/pull/206#issuecomment-1595894959, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALBHSFCLQCFVGXVMOZWD4DXLY75JANCNFSM5RSLZCZQ . You are receiving this because you authored the thread.Message ID: @.***>
This issue is no longer marked for closure.
I ended up adding a custom data directory to the molecule tests, which is why everything else is failing in the PR.
What would be the best way to handle the __postgresql_config_path: "/var/lib/pgsql/data"
that won't exist if you use a custom directory? Would it make sense to have __postgresql_config_path:
be __postgresql_config_path: "{{ postgresql_data_dir }}"
?
This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
not stale
On Fri, Oct 27, 2023 at 2:57 PM github-actions[bot] < @.***> wrote:
This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post https://www.jeffgeerling.com/blog/2020/enabling-stale-issue-bot-on-my-github-repositories to see the reasons why I mark issues as stale.
— Reply to this email directly, view it on GitHub https://github.com/geerlingguy/ansible-role-postgresql/pull/206#issuecomment-1783435545, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALBHSE4JMJVNW34EYG6ZMDYBQG2PAVCNFSM5RSLZCZ2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZYGM2DGNJVGQ2Q . You are receiving this because you authored the thread.Message ID: @.***>
This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
no stale
So it's failing on the EL versions because __postgresql_config_path
is defaulting to the old data directory I believe?
Is there a way in molecule to have specific variables for the different distros?