unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Olly Betts <olly@survex.com>
To: David Bremner <david@tethera.net>
Cc: Thomas Schwinge <thomas@schwinge.name>,
	notmuch@notmuchmail.org, xapian-discuss@lists.xapian.org
Subject: Re: Transitioning notmuch/Xapian from 32-bit to 64-bit system
Date: Tue, 9 Jul 2019 23:59:49 +0100	[thread overview]
Message-ID: <20190709225949.kjfucm2uccmxs3zx@survex.com> (raw)
In-Reply-To: <87lfx76ukc.fsf@tethera.net>

On Tue, Jul 09, 2019 at 01:28:51PM -0300, David Bremner wrote:
> Thomas Schwinge <thomas@schwinge.name> writes:
> 
> > sizes?).  Doing some light (read-only!) testing, it seems to work fine to
> > access the old 32-bit built Xapian "chert" database with 64-bit
> > notmuch/Xapian.  Is that (a) generally safe and expected to work fine,
> > (b) there may be issues, or (c) don't do that, or don't know?
> 
> IIRC, Olly previously confirmed that the Xapian database is architecture
> independent.

Yes.

[...]
> 
> > (Of course, I'll eventually want to rebuild the database, to take
> > advantage of several new features both on the notmuch and Xapian sides,
> > but I'd prefer to do that later.)
> >
> 
> It would be wise to make a backup with "notmuch dump" before going much further.

You can convert the database at the Xapian level:

https://getting-started-with-xapian.readthedocs.io/en/latest/advanced/admin_notes.html#converting-a-chert-database-to-a-glass-database

However that probably doesn't allow taking advantage of all the new
notmuch features, so it's probably better to dump the tags, reindex
then restore the tags.

Cheers,
    Olly

      reply	other threads:[~2019-07-09 23:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09 14:21 Transitioning notmuch/Xapian from 32-bit to 64-bit system Thomas Schwinge
2019-07-09 16:28 ` David Bremner
2019-07-09 22:59   ` Olly Betts [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190709225949.kjfucm2uccmxs3zx@survex.com \
    --to=olly@survex.com \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    --cc=thomas@schwinge.name \
    --cc=xapian-discuss@lists.xapian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).