Jira (PDB-1130) mechanism to apply non-migration database operations across subsequent upgrades

[Wyatt Alt (JIRA)]

Wyatt Alt created an issue

PuppetDB / PDB-1130 mechanism to apply non-migration database operations across subsequent upgrades Issue Type: New Feature Affects Versions: PDB 2.2.2 Assignee: Unassigned Created: 2015/01/23 10:02 AM Priority: Normal Reporter: Wyatt Alt Customer success sometimes runs manual operations on customer databases, such as CLUSTER in the context of PDB-959. These changes can be lost during upgrades, so to ensure the effects are retained we should formalize a way to track them and hook them into the migration process. Add Comment

This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)

[Kenneth Barber (JIRA)]

Kenneth Barber updated an issue

PuppetDB / PDB-1130 mechanism to apply non-migration database operations across subsequent upgrades

Change By: Kenneth Barber Affects Version/s: PDB 2.2.2

Add Comment

[Russell Mull (JIRA)]

Russell Mull commented on PDB-1130

Re: mechanism to apply non-migration database operations across subsequent upgrades Charlie Sharpsteen Nick Walker Care to comment on this? I could see adding a "post-migrate.d" dir full of sql scripts or something, but would like to collect some actual use cases first.

Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-1130

mechanism to apply non-migration database operations across subsequent upgrades

Change By: Russell Mull Labels: triaged

Add Comment

[Charlie Sharpsteen (JIRA)]

Charlie Sharpsteen commented on PDB-1130

Re: mechanism to apply non-migration database operations across subsequent upgrades The one thing I can think of off the top of my head is that an upgrade might be a good window to run some general maintenance like re-building indices. Nick has some of this in his pe_databases module: https://github.com/npwalker/pe_databases#maintenance

Add Comment

[Moses Mendoza (JIRA)]

Moses Mendoza updated an issue

PuppetDB / PDB-1130

mechanism to apply non-migration database operations across subsequent upgrades

Change By: Moses Mendoza Labels: triaged

Add Comment

[Nick Walker (JIRA)]

Nick Walker commented on PDB-1130

Re: mechanism to apply non-migration database operations across subsequent upgrades The way I've been handling this so far is via puppet code. https://github.com/npwalker/pe_databases/blob/master/manifests/postgresql_settings.pp https://github.com/npwalker/pe_databases/blob/add_fillfactor_setting_to_indexes/manifests/postgresql_settings/index_settings.pp The original case that's mentioned around CLUSTER turned out to not be specific to CLUSTER but to rebuilding the table. I'm not sure we have a need for this? We do have a need to make indexes sometimes but I think that's also better handled by puppet code.

Add Comment

[Claudia Petty (Jira)]

Claudia Petty updated an issue

PuppetDB / PDB-1130

mechanism to apply non-migration database operations across subsequent upgrades

Change By: Claudia Petty Labels: new-feature

Add Comment

This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)