Andrew Hammond wrote:
> Hello All,
>
> I've been working on designing a tool to facilitate both developers
> and operations staff working with slony replicated databases. I think
> that the problem described below is a general problem for people
> working with systems that are both in production and under on-going
> development / maintenance. As a result I would like to both solicit
> the input of the community and share the results. Documentation (which
> is still somewhat drafty) follows.
Andrew,
I think this is a useful idea, that I would be interested in trying myself.
One suggestion: It would be great if there was an option for the
"downgrade" path to be determined automatically, or ignored as option.
I think in some scenarios, it's just not very practical to "go back"
without restoring from a dump file of the old state.
Perhaps there could be some integration with a "diff" tool like APG?
http://pgfoundry.org/projects/apgdiff
Given two databases schemas, it could generate /both/ upgrade and
downgrade paths.
That would work for some simple cases, and manual changes could be used
for more complex cases, which as were data needs to be changed and
changed back as part of an upgrade/downgrade.
Thanks again for your work on this tool!
Mark
