UpStare version UPSTARE_RELEASE_0-12-4 adds the option of producing either a source code evolution report (which shows only how the source code changed) or a diff report (which shows which functions should be updated, e.g. because a datatype used by the function has changed).
UpStare
UpStare 0.12.3
UpStare version UPSTARE_RELEASE_0-12-3 adds support for an update model of lazy updates, support for dynamic stack tracing, the ability to define runtime update constraints that can be useful for minimizing state mappings, for type-safety, and for transaction-safety, the option of marking some functions to not be instrumented for stack reconstruction, and clarifies in the documentation that the default compilation flags of dynamic update patches should use -fPIC.
UpStare 0.11.6 experiments
The experiments studied by UpStare are now available, based on version UPSTARE_RELEASE_0-11-6.
UpStare 0.10.9
UpStare version UPSTARE_RELEASE_0-10-9 considerably improves the ability of the patch generator to automatically produce stack transformers and incorporate user-defined stack transformers. It also implements support for blocking system calls in a much more efficient way.
UpStare 0.9.12
UpStare version UPSTARE_RELEASE_0-9-12 fixes a critical issue in the runtime in determining which children have died and should be ignored when coordinating an update with children. It also handles as non-blocking file descriptors created with open() and pipe(), and calls to select() with a pointer (possibly set to NULL) timeout argument that would block indefinitely.
With these changes the system can update PostgreSQL while multiple clients are connected to it.