1)
Index Cond: ("outer".physmessage_id = p.id)
Total runtime: 15.337 ms
(28 rows)
My primary concerns:
- Are there any reasons why we need to only look at the first 255 characters
of the header name?
- Are there any reasons why we would be looking for the stri
By paul at nfg:
> With the change you did, imap-search on substrings will be broken.
I think I'm OK with that. Logically, I'd think that would come up in
something like a webmail scenario but I'd hope my local e-mail client
would do that on my machine instead of the server.
> Please keep
By decibel at decibel:
- What version of PostgreSQL are you using? I'm somewhat surprised that
- it's not doing any bitmap scans.
I'm running 8.0.13. I'm not too familiar with bitmap scans. What
queries in the system (aside from the one I was looking at) should be
using them?
- BTW, RAID5
ally
delete mail, I just move the spam to the spam folder and save
everything so I haven't had time to check to see whether single
deletions work. Is anyone else having the same issue? If it's
already in the bug tracker I apologize, it's been a long time since I
went
y with the less
than operator instead of IN/OR. I'll keep digging and see if I can find a
more efficient way.
Thanks,
Tim Mattison
= 0
MESSAGE_STATUS_SEEN= 1
MESSAGE_STATUS_DELETE = 2
MESSAGE_STATUS_PURGE = 3
MESSAGE_STATUS_UNUSED = 4
MESSAGE_STATUS_INSERT = 5
MESSAGE_STATUS_ERROR = 6
So, my question is... is this the right place to suggest performance
tweaks to SQL statements? If not, where/to whom can I send this?
Thanks,
Tim Mattison
[EMAIL PROTECTED]
out dbmail
That's the version of the source that came up with this issue.
On Mon, 2004-11-15 at 12:41 -0500, Matthew T. O'Connor wrote:
> Tim Mattison wrote:
>
> >I've been using DBMail for a while now and I upgraded to 2.0+ (whatever
> >the CVS HEAD is) and I star
he IMAP server is
completely unusable on my server. Am I the only one that has had this
problem? I must also note that I'm using PostgreSQL so if you're using
MySQL it may not come up.
Just thought I'd get all this out there so someone could see what's
going on.
--
Tim Mattison <[EMAIL PROTECTED]>
Mattison & Rosenthal Consulting Inc.
