On 21/06/2012, at 1:51 AM, Jason Guiditta wrote:
On 21/06/12 01:45 +1000, Justin Clift wrote:
> On 21/06/2012, at 1:27 AM, Javier Pena wrote:
> <snip>
>> RHEV-M is following a very similar approach. They have psql scripts covering each
database schema change since the first release, and each new package applies the delta
between schema versions. According to our local RHEV-M developer, Eli Mesika designed this
schema, so you may want to contact him for more details.
>
> It's definitely a useful data point. Have seen this approach used for
> other applications before, and work well. Not fast, but does the job.
>
> + Justin
How does this approach handle making sure no service is touching the
database while the upgrade happens, and that any such services get
restarted afterward so they continue to work?
No idea of the details. I just remember seeing the output from this kind
of thing in log files, where it's showing the application of db deltas
during upgrades. ;)
+ Justin
--
Aeolus Community Manager
http://www.aeolusproject.org