Hello everyone,
I heard about DBmail on Freshmeat Monday and decided to try it out.
It seems to have promise. But I found a few things that I hope will help make
using it a bit better.
1. the build.sh has 3 errors in it. lines 65. 68 I believe there needs to be
a space after that [ so it reads
Brett (Mare) Henley wrote:
Hello everyone,
I heard about DBmail on Freshmeat Monday and decided to try it out.
It seems to have promise. But I found a few things that I hope will help make
using it a bit better.
1. the build.sh has 3 errors in it. lines 65. 68 I believe there needs to be
a s
On Tuesday, Oct 14, 2003, at 20:16 Europe/Amsterdam, Paul J Stevens
wrote:
Brett (Mare) Henley wrote:
I built Postgres7.4Beta (yes I know it's beta code) for the db. And
tried to
I used thunderbird 0.2 as my mail agent to test out the imap4
functions. and
I'm not sure if i'm not abusing th
Ilja Booij wrote:
The tables are fixed in CVS. For people using the DBMail 1.2 release: I've
put Paul's SQL-script on http://www.dbmail.org so you can download it, and
run it against your PostgreSQL DBMail database.
This update script can also be found in the sql/postgresql/ directory in
the s
On Wed, Oct 15, 2003 at 03:25:59PM +0200, Paul J Stevens wrote:
> Caveat: I'm no sql guru.
> Rule of thumb: all fields used in where clauses should be indexed.
True.
> mysql has a nice sql command called 'explain select ...' which analyzes
> usage of indexes for select queries. I don't know of a
ge that is being inserted, and drop unique_id out of the
indexes completely (well, except for the one index that is supposed
to be for that field)). I was planning on working on it, but kind
of ran out of time.
Jn
Original Message
From: Paul J Stevens
To: dbmail@dbmail.org
Subject: Re:
On Wed, 2003-10-15 at 09:37, Patrick Giagnocavo +1.717.201.3366 wrote:
> I think that (depending on PG version) adding a primary key will
> create a unique index on that field. A primary key has to be unique,
> so creating a unique index enforces that requirement.
It is, when you make a column a
On Wed, 2003-10-15 at 09:25, Paul J Stevens wrote:
> Caveat: I'm no sql guru.
> Rule of thumb: all fields used in where clauses should be indexed.
Not exactly true... Every time you create an index it slows down
inserts and updates (again something that will be helped with the new
phy_message tab
On Wednesday, Oct 15, 2003, at 16:22 Europe/Amsterdam, Jesse Norell
wrote:
Ilja,
There have been various discussions in the past on the lists
reguarding indexing issues... I don't remember all the issues,
but a couple items that come to mind are:
1) It would be nice to provide multiple index
> > 1) It would be nice to provide multiple index sets - most of
> > the ones that have been posted are good for imap, but almost
> > entireley extra overhead if you just use pop3. We've improved
> > our pop3 performance by removing most of them and perhaps
> > optimizing a couple (or they may b
From: "Jesse Norell" <[EMAIL PROTECTED]>
> Having said that, I think it was dbmail-smtp performance we
> improved by removing those indexes (ie. because the database doesn't
> have as many indexes to maintain). I think we did do some optimizing
> for pop3 too, though, but I don't know that it (i
From: "Jesse Norell" <[EMAIL PROTECTED]>
> Having said that, I think it was dbmail-smtp performance we
> improved by removing those indexes (ie. because the database doesn't
> have as many indexes to maintain). I think we did do some optimizing
> for pop3 too, though, but I don't know that it (i
On 15-okt-03, at 19:13, Matthew T. O'Connor wrote:
From: "Jesse Norell" <[EMAIL PROTECTED]>
Having said that, I think it was dbmail-smtp performance we
improved by removing those indexes (ie. because the database doesn't
have as many indexes to maintain). I think we did do some optimizing
fo
On Wed, 2003-10-15 at 17:12, Eelco van Beek - IC&S wrote:
> none of the dbmail processes does a DELETE. Only maintenance does that
True, but it does do an update to the messages table, which is worse. An
update is equivalent to performing a delete and an insert (I think).
> True, but it does do an update to the messages table, which is worse. An
> update is equivalent to performing a delete and an insert (I think).
Only where postgres memory management is concerned, afaik. I
don't think there are any negative repercussions under mysql.
And the messages table is
15 matches
Mail list logo
