similar to: postlist chunking

Greetings, Using latest svn. I've noticed the following error when performing index merging: postlist: baseB blocksize=8K items=33962 lastblock=534 revision=1 levels=2 root=459 B-tree checked okay Tag containing meta information is corrupt. postlist table errors found: 1 I can still search on this index (I've only checked very small indexes), but merging is now a problem since I check

Hi, I do have few questions regarding xapine as I'm a newbie in this and would appreciate if someone could give me some insight: 1: When I'm trying to index , why it creates/opens so many files, e.g.this is how one of my index looks like: % ~/xapian_index> ls db_lock position_baseA record_DB termlist_baseA meta postlist_DB record_baseA value_DB

hi, I'm using Xapian on Windows with large files. My index directory is about 65 607 466 693 bytes: 2007-01-30 09:28 17 position_baseA 2007-01-30 10:06 17 position_baseB 2007-01-23 14:18 0 position_DB 2007-01-30 10:06 360 496 postlist_baseB 2007-01-30 10:06 23 623 852 032 postlist_DB 2007-01-30 10:06 88 432

Hi guys I have implemented xapian on a website, and it currently has about 2M items in its index. Its all been working quite nicely so far, until I tried removing some old items from the index (removing items when the index was smaller was no problems at all). When I try to remove them now (using writabledatabase_delete_document() via php), it halfway freezes up the machine, and the apache

Hi, using dovecot-2.0.9-7.el6.x86_64 on CentOS release 6.5 (Final) I have an issue with thunderbird imap chunking. Some attachments are corrupted, because Thunderbird is just storing the first chunk. Since there are some workarounds by editing the "mail.imap.fetch_by_chunks" via about:config this is not the best choice for me because every client has to be edited. Is there a way to set

Hi, It seems that there is an issue with the submission service when the SMTP server advertises chunking (I use Exim v4.91). I tried this with Dovecot v2.3.3 and current master and could reproduce it with both versions. My setup is that dovecot submission proxies to Exim on port 10025. The first mail gets through without any issues, but the second email will not get send. I had this issue at

Op 20/09/2018 om 13:39 schreef Michael Goth: > On 09/20/2018 12:56 PM, Robert Schetterer wrote: >> Am 20.09.2018 um 11:04 schrieb Michael Goth: >>> Hello, >>> >>> I'm setting up Dovecot 2.3.2.1 as a submission proxy to a Postfix >>> backend server. Dovecot announces CHUNKING, but the Postfix backend >>> does not support (or announce) it.

Am 20.09.2018 um 11:04 schrieb Michael Goth: > Hello, > > I'm setting up Dovecot 2.3.2.1 as a submission proxy to a Postfix > backend server. Dovecot announces CHUNKING, but the Postfix backend does > not support (or announce) it. > > HELO from Postfix: > > ? 220 backend.mydomain.com ESMTP Postfix (Ubuntu) > ? ehlo test > ? 250-backend.mydomain.com >

Greets, I've encountered the following while performing test merges (and writing code to handle errors, etc so things can be automated) and wondering about the best way to proceed: xapian-compact -b64k -m src1 src2.... tmp_dst -- works as expected, exit code 0. xapian-check tmp_dst -- produces the following error for the postlist: postlist: baseB blocksize=64K items=28175410

Hello, I'm setting up Dovecot 2.3.2.1 as a submission proxy to a Postfix backend server. Dovecot announces CHUNKING, but the Postfix backend does not support (or announce) it. HELO from Postfix: 220 backend.mydomain.com ESMTP Postfix (Ubuntu) ehlo test 250-backend.mydomain.com 250-PIPELINING 250-SIZE 104857600 250-VRFY 250-ETRN 250-STARTTLS

On 09/20/2018 10:24 PM, Stephan Bosch wrote: > > > Op 20/09/2018 om 13:39 schreef Michael Goth: >> On 09/20/2018 12:56 PM, Robert Schetterer wrote: >>> Am 20.09.2018 um 11:04 schrieb Michael Goth: >>>> Hello, >>>> >>>> I'm setting up Dovecot 2.3.2.1 as a submission proxy to a Postfix >>>> backend server. Dovecot

On Fri, Dec 29, 2017 at 03:00:47PM +0000, David Edmondson wrote: > Running notmuch from git on Debian testing[1] with the mail and database > sitting on a ZFS filesystem, adding mail to a new database: > > > agrajag-testing ~/s/notmuch % ./notmuch new > > Found 605510 total files (that's not much mail). > > add_file: A Xapian exception occurred36m 37s remaining).

On Thu, Jan 31, 2019 at 08:44:44PM +0100, Jean-Francois Dockes wrote: > I have run a number of tests, with data mostly from a project gutenberg dvd > and other books, with relatively modest index sizes, from 1 to 24 GB. > > Quite curiously, in this zone, with all Xapian versions I tried, the ratio > from index size to the amount of writes is roughly proportional to the index >

Olly Betts writes: > On Mon, Apr 11, 2016 at 09:54:36AM +0200, Jean-Francois Dockes wrote: > > The question which remains for me is if I should run xapian-compact > > after an initial indexing operation. I guess that this depends on the > > amount of expected updates and that there is no easy answer ? > > I think it's not obvious whether it's a good plan

On 09/20/2018 12:56 PM, Robert Schetterer wrote: > Am 20.09.2018 um 11:04 schrieb Michael Goth: >> Hello, >> >> I'm setting up Dovecot 2.3.2.1 as a submission proxy to a Postfix >> backend server. Dovecot announces CHUNKING, but the Postfix backend >> does not support (or announce) it. >> >> HELO from Postfix: >> >> ?? 220

Hi, The size of the string generated by VSEncoder is 12592387, while that by InterpolativeEncoder is 8554817. When only encoding the first 1000lines, both cost 0ms to decode and VS cost 1ms to encode while Interpolative cost 0ms, 1000lines is just too little to catch the difference in my test. I upload the source code to https://github.com/HurricaneTong/Xapian/tree/master/VSEncoder The

On Wed, Jun 19, 2013, at 03:49 PM, Olly Betts wrote: > On Wed, Jun 19, 2013 at 01:29:16PM +1000, Bron Gondwana wrote: > > The advantage of compact - it runs approximately 8 times as fast (we > > are CPU limited in each case - writing to tmpfs first, then rsyncing > > to the destination) and it takes approximately 75% of the space of a > > fresh database with maximum

I've some problems converting a xapian db, created with core 1.1.3 (using chert), to the new chert format. I'm using xapian-chert-update, compiled from the core-1.2.4. The conversion seems to run without errors: #./xapian-core-1.2.4/bin/xapian-chert-update old new postlist: Reduced by 33.3333% 16K (48K -> 32K) record: Size unchanged (8K) termlist: doesn't exist position: Size

Xapians, I am maintaining about two indexes for my search engines which approximately is each the same size. I would like to share this knowledge with you, since many of you have never seen Xapian index of this size. And of course you can search the index by yourself at - http://myhealthcare.com/ - http://find1friend.com/ I need 2 x 100 million more documents into each index, and I hope it will

Since a couple of weeks we are experiencing occasional segmentation faults within Xapian 1.5. We can't reproduce the crashes, but we have strong hints that they are due to memory corruption. We have narrowed down our root cause analysis to phrase searches on multi-databases that fail on reading the `hint` field in the`QueryOptimiser`class [1]. We'd appreciate any hints on how to fix this.