DBMail folks,
I'm signing off this list because I ended up using AOX rather than
DBMail. However, I'm available to answer specific PostgreSQL
troubleshooting issues if you e-mail me directly, or find me on
IRC.freenode.net (agliodbs).
--
Josh Berkus
PostgreSQL Experts Inc.
www.pge
> In MySQL (using InnoDB engine) there is no difference for between COUNT(*) or
> COUNT(1)
> because it is 'optimized' to use the PRIMARY index.
FWIW, there's no difference in PostgreSQL either.
--Josh
___
DBmail mailing list
DBmail@dbmail.org
http:/
Paul,
DBMail-2.2 doesn't use \\ escaping, and hasn't done so for quite some
time. All strings are escaped using PQescapeString and PQescapeBytea
which I assume will produce safe queries. So in my understanding the
postgres warning is a false positive. But - Josh - please correct me if
I'm wrong.
Peter Rabbitson wrote:
Josh Berkus wrote:
However, the reason why we added the warning is that we figured out in
2006 that \\ escapes are a SQL injection vulnerability (this goes for
MySQL as well). It's possible by version 8.5 (2010) PostgreSQL will
stop supporting them.
Interesting..
Angel,
Sample from my logs (In Spanish)
...
HINT: Use '' para escribir comillas en cadenas, o use la sintaxis de escape de
cadenas (E'\\').
WARNING: uso no estandar de \\ en un literal de cadena
LINE 1: ..., messageblk,blocksize, physmessage_id) VALUES (1,'Received:...
...
Well, you can get
Colin,
Is this the advisable way to approach this problem in the first place?
If so, what do I need to do to get that master user going?
What about using dspam, which is database-based? Then you could simply
do a query-based table copy.
Also, keep in mind that this scheme will require you
Paul,
> I'm pretty sure though that IMAP SEARCH will be broken if you use
> sql-ascii.
Hmmm. Not if you're just executing it as "LIKE" queries, and the search
terms don't include non-ascii characters.
--
--Josh
Josh
eryx
Different features. I'm actually currently considering achiveopterix because
Abjhit already has full text search and virtual folders working.
--
Josh Berkus
PostgreSQL
San Francisco
___
DBmail mailing list
DBmail@dbmail.org
https://mailm
No.
> or is =ddl enough?
DDL is for schema changes, like ALTER TABLE. That doesnt' do you any good
for this.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
___
DBmail mailing list
DBmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
Michael,
It could be we can find other optimzations as well. Paul, is there a
simple way to log all DB queries to a separate file? Like this, we
could log for a typical day, and then see which are the most queries
and where we could start to optimize. I know you, Paul, have other
things to do
Paul,
2) Wouldn't the query be much faster if the
ENCODE(k.messageblk::bytea,'escape') LIKE '%sim%' was in the WHERE
clause instead of the HAVING clause?
Try it. Afaik, it simply wont work.
That depends on whether you're trying to return just a list of IDs, or
the full contents of the messa
Paul,
> Very good question. The only solution I can think of is full text indexing.
I'll take a stab at this once I have my server up and running. Necessarily,
though, the solution will be database-specific.
--
Josh Berkus
PostgreSQL
San F
gt; Marginal at best.
Hmmm. If you're storing stuff as MIME, you could actually put it in a TEXT
field in PostgreSQL. Mind you, that just makes replication easier, it
doesn't help otherwise -- both are stored using TOAST regardless.
--
-
in, things may be not quite that bad after all.
> I havent figured it out quite yet. Which makes it just one of those
> things: they take time to work themselves out.
Hmmm. I don't know mime parsers *at all*. Are you storing the attachments
in MIME form, or in ori
Aaron Stone wrote:
On Jun 25, 2008, at 10:16 AM, Josh Berkus wrote:
Paul,
Don't use it for anything other than testing. There are still some
pretty fundamental issues to iron out.
Thanks for the warning. 2.2 it is. Now, if only Ubuntu would update
the $&%&@ packages ...
Paul,
Don't use it for anything other than testing. There are still some
pretty fundamental issues to iron out.
Thanks for the warning. 2.2 it is. Now, if only Ubuntu would update
the $&%&@ packages ...
2) If I run queries against the mail in the backend database, and update or
delete
reSQL? What do you think
of egroupware?
5) If I added full text search to the backend database, any thoughts on how
I could expose this to the mail client?
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
___
DBmail mailing list
DBmail@dbmail.org
http
17 matches
Mail list logo