timmattison wrote:
>
> Paul J Stevens wrote:
>> What do you mean by 'moving messages between IMAP'. Imapsync, perhaps?
>>
>
> Yikes. Didn't proofread that part. I meant to say 'moving messages between
> IMAP folders'. That's where the bottleneck is.
Still doesn't compute. Moving messages in IMAP normally means COPY/STORE
if it's within the same account, or FETCH/APPEND if it's being done
between accounts.
like:
X SELECT SomeMailbox
X COPY 1:* OtherMailbox
X STORE 1:* (\Deleted)
and for neither SEARCH is required.
So, how are you trying to move messages? Not that it will speed up
SEARCH, but we might be able to solve your bottleneck problem.
> If it requires substring matching I think we're stuck. I haven't seen a
> reliable way to get PostgreSQL to use indexes when doing these kinds of
> queries unless you manually change the ENABLE_SEQSCAN parameter. That
> really doesn't provide any benefit when the query planner can't think of a
> good way to use your index in the first place.
The relevant quote form the RFC:
6.4.4. SEARCH Command
....
In all search keys that use strings, a message matches the key if
the string is a substring of the field. The matching is
case-insensitive.
....
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
Dbmail-dev mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
