Skip to content
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

Locale generation requires restart, otherwise SQL commands fail #342

Open
hakoerber opened this issue Apr 17, 2018 · 3 comments
Open

Locale generation requires restart, otherwise SQL commands fail #342

hakoerber opened this issue Apr 17, 2018 · 3 comments
Labels

Comments

@hakoerber
Copy link

When the locale is not present when the role is run, it is generated, as required. The problem is that postgresql is not restarted afterwards, which makes subsequent commands like CREATE TABLE fail with a locale error.

This issue is not yet actionable, I will gather more information as soon as I can.

@hakoerber hakoerber changed the title Locale generation requires restart, otherwise SQL commands fail. Locale generation requires restart, otherwise SQL commands fail Apr 17, 2018
@gclough
Copy link
Collaborator

gclough commented Apr 17, 2018

@hakoerber, I've messed with the restart/reload mechanism in #294, but it's not been merged yet. Unfortunately the advice was to push all restart/reloads into handlers, which will only fire at the end.

If you're wanting to do a restart in the middle of the play, then you'll have to do it manually like in #331... but I've tried to introduce the concept in #294 that we should only restart when the postgresql_restart_on_config_change parameter is true... and I can see why you would want to force a restart, but then it becomes a question of whether we honour the requirement to have this locale change and restart the cluster... or honour the "create no downtime unless instructed" ethos I've tried to use in #294.

Can you provide an example of exactly what you're doing, and the error?

@hakoerber
Copy link
Author

Hey sorry, looks like I lost track of this.

I think this can be closed.

Copy link

This issue 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!

@github-actions github-actions bot added the stale label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants