postgres creates roles and databases in the `post-start` script now. about postgres-release

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/155047266

The labels on this github issue will be updated when the story is started.

[valeriap]

@chhhavi
Thanks for reporting it.
We did this change to fix an issue related to not reporting back an error in creating/updating roles and databases. The monit job is currently linked directly to the PostgreSQL status, behaviour that I would prefer not to change, and eventual failures in the control job after the PostgreSQL start were ignored. Considering that this action is not needed at each start but only after a deployment, the post-start looked as the good place.
But I got your concern that it's related to colocating the postgres job with the client that uses it and we will take this scenario into account.

[valeriap]

@chhhavi
We are currently working on a feature that introduces hooks that are invoked before and after postgreSQL start and stop.
The post-start hook could be used to create the databases and roles earlier.
Would the usage of this hook be sufficient for your use case?

[chhhavi]

This looks like this could work for our use case.

[vito]

@valeriap Will using the new feature require people using this release to configure something in order to support co-location? Or will this be back to working as it did before by default?

[valeriap]

@vito we went further on this issue and we introduced a new monit process dedicated to roles and db creation. See commit.
With this new process no additional configuration is needed for co-location.
We will bump a new release with this change soon.

[valeriap]

Closing the issue since v27 is available.
Please reopen if you still see issues.