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

*: Only use PGParameters from the cluster spec. #181

Merged
merged 1 commit into from
Nov 9, 2016

Conversation

sgotti
Copy link
Member

@sgotti sgotti commented Nov 8, 2016

With this patch the postgresql.conf will only include the defined
pgParameters in the cluster spec and will not include other config files
anymore.

This makes the postgres config handling more consistent and let us really
handle it in a centralized fashion without surprises.

When initializing a cluster we'd like to retain the previous pg
parameters:

  • When initMode is new: the one created by initdb when initializing a new db
  • When initMode is existing: the current instance parameters
  • When handling point in time recovery: the parameters provided by the
    restored instance.

For doing this, the keeper will, during initialization, rename and
include the existing postgresql.conf, get the list of the modified
parameters, report them to the sentinel that will merge them back in the
cluster spec.

@sgotti sgotti force-pushed the only_cluster_spec_pgparameters branch 4 times, most recently from b312f3c to 1e5dcea Compare November 9, 2016 14:07
With this patch the postgresql.conf will only include the defined
pgParameters in the cluster spec and will not include other config files
anymore.

This makes the postgres config handling more consistent and let us really
handle it in a centralized fashion without surprises.

When initializing a cluster we'd like to retain the previous pg
parameters:

* When initMode is new: the one created by initdb when initializing a new db
* When initMode is existing: the current instance parameters
* When handling point in time recovery: the parameters provided by the
restored instance.

For doing this, the keeper will, during initialization, rename and
include the existing `postgresql.conf`, get the list of the modified
parameters, report them to the sentinel that will merge them back in the
cluster spec.
@sgotti sgotti force-pushed the only_cluster_spec_pgparameters branch from 1e5dcea to a06394a Compare November 9, 2016 14:08
@sgotti sgotti merged commit a06394a into sorintlab:master Nov 9, 2016
sgotti added a commit that referenced this pull request Nov 9, 2016
*: Only use PGParameters from the cluster spec.
@sgotti sgotti modified the milestone: v0.5.0 Dec 12, 2016
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.

None yet

1 participant