Return-Path: <tomi.ollila@iki.fi>
X-Original-To: notmuch@notmuchmail.org
Delivered-To: notmuch@notmuchmail.org
Received: from localhost (localhost [127.0.0.1])
	by olra.theworths.org (Postfix) with ESMTP id 4A0AD431FBF
	for <notmuch@notmuchmail.org>; Mon, 17 Mar 2014 23:58:06 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
	autolearn=disabled
Received: from olra.theworths.org ([127.0.0.1])
	by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CzA3Hgv2Rclg for <notmuch@notmuchmail.org>;
	Mon, 17 Mar 2014 23:57:58 -0700 (PDT)
Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])
	by olra.theworths.org (Postfix) with ESMTP id AB375431FBD
	for <notmuch@notmuchmail.org>; Mon, 17 Mar 2014 23:57:58 -0700 (PDT)
Received: from guru.guru-group.fi (localhost [IPv6:::1])
	by guru.guru-group.fi (Postfix) with ESMTP id 0A1ED10009D;
	Tue, 18 Mar 2014 08:57:51 +0200 (EET)
From: Tomi Ollila <tomi.ollila@iki.fi>
To: Rob Browning <rlb@defaultvalue.org>, Jani Nikula <jani@nikula.org>,
	David Bremner <david@tethera.net>,
	Jameson Graef Rollins <jrollins@finestructure.net>,
	Notmuch list <notmuch@notmuchmail.org>
Subject: Re: WARNING: database upgrade coming
In-Reply-To: <874n2w59c0.fsf@trouble.defaultvalue.org>
References: <874n37a017.fsf@zancas.localnet>
	<87txawkam3.fsf@servo.finestructure.net>
	<87a9cood0l.fsf@nikula.org> <87eh20v7zc.fsf@zancas.localnet>
	<877g7so6kj.fsf@nikula.org>
	<874n2w59c0.fsf@trouble.defaultvalue.org>
User-Agent: Notmuch/0.17+155~g3416ef5 (http://notmuchmail.org) Emacs/24.3.1
	(x86_64-unknown-linux-gnu)
X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL
	$[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F
	!)g;OY^,BjTbr)Np:%c_o'jj,Z
Date: Tue, 18 Mar 2014 08:57:50 +0200
Message-ID: <m2ha6whu35.fsf@guru.guru-group.fi>
MIME-Version: 1.0
Content-Type: text/plain
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Use and development of the notmuch mail system."
	<notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Mar 2014 06:58:06 -0000

On Tue, Mar 18 2014, Rob Browning <rlb@defaultvalue.org> wrote:

> Jani Nikula <jani@nikula.org> writes:
>
>> Something like this? Just insert text that makes sense to the user. ;)
>
> If you decide to go this route, I wonder if it might also be worth
> adding the text about interruption being OK.

In addition it could just start the upgrade, and if the total time of
upgrade is less than 10 seconds it would wait until that time gets
up and then replace the old database with the new one.

But very informative and verbose messages of how safe the interruption
of database is would be in order...

Some ideas to bikeshed with:

"The database upgrade is done in a new database; at the end of the updrade
the current database is replaced with the new one -- Interrupting updrade
(with Ctrl-C) leaves you with the current database."

> -- 
> Rob Browning

Tomi