Ah, we need to do a better job documenting this for sure. I think you _cannot_ 
do an in-place downgrade because the on-disk header format changed to v7 to 
include some metadata needed for the purge feature that was re-introduced in 
2.3.0:

https://github.com/apache/couchdb/commit/78a388d 
<https://github.com/apache/couchdb/commit/78a388d>

Bill’s suggestion of replication is probably going to be the way to go here. 
Someone more familiar with the disk format version changes and upgrade / 
downgrade logic might correct me, but this is my current understanding.

Adam

> On Feb 4, 2019, at 3:21 PM, Bill Stephenson <b...@cherrypc.com.INVALID> wrote:
> 
> Have you tried replicating your data to the 2.2.1 DB?
> 
> 
> Bill
> 
> 
> 
>> On Feb 4, 2019, at 2:19 PM, Compu Net <compu...@48th.com> wrote:
>> 
>> Can a couched 2.3.0 be downgraded to 2.1.1 without changes to the data ?
> 

Reply via email to