Hi,
I’ve been seeing the same ‘V' error recently, with:
- Archiveopteryx version 3.2.0
- postgresql 9.3
- Ubuntu 14.04.3 LTS
I’m in the process of migrating ~175 Gb of emails (~20 accounts) from a dovecot
system to sox using imapsync, with many more issues than I had expected. The
imapsync program has complained often of losing connection to sox, or have
dropped connections after waiting 120s for a reply.
Also when doing an account-to-account content comparison with a python script,
I’ve noticed that the dovecot server (v2.2.9) is approximately 2x faster at
responding to a
"FETCH BODY[HEADERS]" than Archiveopteryx, all that with both software running
on same machine/hard disks.
Regards,
Hugo
> On 12 Sep, 2016, at 13:08, Tom Ivar Helbekkmo <[email protected]> wrote:
>
> Yesterday, I noticed some strange error messages in my PostgreSQL and
> Archiveopteryx logs. I don't know how long it's been like this, but I
> upgraded both to fresh versions (aox to HEAD of git "master" branch,
> pgsql to 9.5.3), with no change in behavior.
>
> I use Gnus to read my email, and the problem occurs once per mailbox
> whenever I ask Gnus to refresh its view of them. Here's what it looks
> like with verbose logging:
>
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/287/1 Updating 1 (of 0)
> session(s) on /users/tih/uninett for modseq [1,99115>, UID [1,198>
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1 Starting session on mailbox
> /users/tih/uninett
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/287/1 Dequeueing query
> "select first_recent from mailboxes where id=$1" ($1='148') on backend 1
> (with 1 rows)
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/287/1 Dequeueing query
> "select mm.uid, mm.modseq from mailbox_messages mm where mm.mailbox=$1 and
> mm.uid<$2" ($1='148',$2='198') on backend 3 (with 197 rows)
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/497/1 Appending flag update
> for modseq>V and UIDs
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/287 Dequeueing query
> "begin" on backend 3
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/497/1 Dequeueing query
> "begin" on backend 2
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/287 Dequeueing query
> "select uid from mailbox_messages mm where mailbox=$1 and not seen order by
> uid limit 1" ($1='148') on backend 3 (with 0 rows)
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/497/1 PostgreSQL Server:
> invalid input syntax for integer: "V"
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/497/1 Execution time 5ms
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/287 Dequeueing query
> "commit" on backend 3
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/287 Execution time 11ms
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/287 91019 OK [READ-ONLY]
> done
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/288 Fetch <=197 messages:
> flags
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/497/1 Dequeueing query
> "commit" on backend 2
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/288 Dequeueing query
> "select f.uid, fn.name from flags f join flag_names fn on (f.flag=fn.id)
> where f.mailbox=$1 and f.uid=any($2)" ($1='148',$2='{1,2,3,4,5,6'..\
> . (681b)) on backend 3 (with 13 rows)
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/288 Dequeueing query
> "select uid, seen, deleted from mailbox_messages where mailbox=$1 and
> uid=any($2)" ($1='148',$2='{1,2,3,4,5,6'... (681b)) on backend 1 (with\
> 197 rows)
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/288 Execution time 10ms
> Sep 12 04:45:33 barsoom Archiveopteryx: 22609/2/1/288 91020 OK done
>
> So, where does that V come from? :)
>
> -tih
> --
> Elections cannot be allowed to change anything. --Dr. Wolfgang Schäuble
>
