On 11-10-12 04:46 AM, Glyn Astill wrote:
>> From: Steve Singer<ssinger at ca.afilias.info>
>
>>
>
>> The second release candidate for 2.1.0 has been released.
>>
>> This release candidate includes only three changes from the last release
>> candidate.
>>
>> - Bug #236 :: Fix default formatting of timestamp in logs
>> - Add support for PostgreSQL 9.1.  Simply marking it a supported version
>> - Bug #237 :: Drop set did not remove truncate triggers.
>>
>> We plan on waiting at least a week before releasing 2.1.0 final.  If no
>> serious issues are found we hope to release 2.1.0 next week or early the
>> following week.
>>
>
> Just out of interest, how complicated will the upgrade path be from 2.0 to 2.1?

In terms of the upgrade procedure it should be similar to the upgrade of 
a minor 2.0.x to 2.0.y type of upgrade ie  install the new version on 
all nodes and run UPDATE FUNCTIONS on all nodes.

You will also need to review all of your slonik scripts to make sure 
they still work, some improperly written slonik scripts won't behave the 
same with the implicit wait for changes.