Postgres vs Mysql

I'm in the process of upgrading my mail server.  In the
past, I've 
always used mysql for Maia.  I'm contemplating moving to
postgres.  My 
thought is to separate functions on the box so I have
Maia's storage in 
postgres and my other database needs in mysql.

Before I do such a thing, are there any benefits or
drawbacks to using 
one database over the other?  I'm not concerned with
migrating existing 
data.  I'm upgrading to a different linux distro, upgrading
from a pre 1 
release of Maia and changing the mail server so retaining
the existing 
data is not a concern.

Thanks in advance,

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.c
om
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Darrick Hartman wrote:
> Before I do such a thing, are there any benefits or
drawbacks to using 

Let the flamewars begin... lol

In my experience, postgres is slower.  Lately there have
been reports of
slowness from both databases concerning the bayes database
implementation, but
throwing that issue aside, I think I have seen mysql
performing slightly better.

Maia involves a lot of writes compared to reads.  (Was was
amazed the other day
watching iostat).  IIRC, Postgres is slower on heavy
writing. (and also needs
the infamous vacumn process)

If anyone has a well tuned postgres server and would like to
counter this
thought, feel free.   (And then
tell us how the heck to tune postgresql
properly! )

- --
David Morton
Maia Mailguard                        - http://www.maiamailguard
.com
Morton Software Design and Consulting - http://www.dgrmm.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFFDra4Uy30ODPkzl0RAmasAJ912/y/qEZk5CRanfWCKgKN3wCM0ACg
obrY
p3zm8STylJ28vP1pMEvgcLw=
=qnXd
-----END PGP SIGNATURE-----
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

On Mon, 18 Sep 2006, David Morton wrote:

> In my experience, postgres is slower.  Lately there
have been reports of 
> slowness from both databases concerning the bayes
database 
> implementation, but throwing that issue aside, I think
I have seen mysql 
> performing slightly better.
>
> Maia involves a lot of writes compared to reads.  (Was
was amazed the 
> other day watching iostat).  IIRC, Postgres is slower
on heavy writing. 
> (and also needs the infamous vacumn process)
>
> If anyone has a well tuned postgres server and would
like to counter 
> this thought, feel free.   (And then
tell us how the heck to tune 
> postgresql properly! )

I'm running things on a PostgreSQL server, having switched
from MySQL a 
little while back ...

0. make sure you run 8.1.x

1. give it lots of shared memory

2. make sure you run the autovacuum daemon

At least, that's all the tuning I've done on her ... and
its running on a 
shared server with other processes running ...

I switched from MySQL due to repeated database corruption on
the MySQL 
side of things ... got tired of having to rebuild it from
scratch ...

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email . scrappyhub.org                              MSN .
scrappyhub.org
Yahoo . yscrappy               Skype: hub.org        ICQ .
7615664
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

Marc G. Fournier wrote:
> On Mon, 18 Sep 2006, David Morton wrote:
>
>> In my experience, postgres is slower.  Lately there
have been reports 
>> of slowness from both databases concerning the
bayes database 
>> implementation, but throwing that issue aside, I
think I have seen 
>> mysql performing slightly better.
>>
>> Maia involves a lot of writes compared to reads. 
(Was was amazed the 
>> other day watching iostat).  IIRC, Postgres is
slower on heavy 
>> writing. (and also needs the infamous vacumn
process)
>>
>> If anyone has a well tuned postgres server and
would like to counter 
>> this thought, feel free.   (And then
tell us how the heck to tune 
>> postgresql properly! )
>
> I'm running things on a PostgreSQL server, having
switched from MySQL 
> a little while back ...
>
> 0. make sure you run 8.1.x
>
> 1. give it lots of shared memory
>
> 2. make sure you run the autovacuum daemon
>
> At least, that's all the tuning I've done on her ...
and its running 
> on a shared server with other processes running ...
>
> I switched from MySQL due to repeated database
corruption on the MySQL 
> side of things ... got tired of having to rebuild it
from scratch ...
I've seen that as well.  My current install has some issues
with innodb 
claiming that log sequence number bla bla is in the future. 
And that my 
database may be corrupt.
My thinking is that if I have mysql and postgres both
running on the 
box, I can leave email users and all sorts of web-based
tools in mysql 
and if I have corruption that would involve taking Maia down
in the 
future, I would not affect the majority of the functions on
this box.  
While an inconvenience, filtering could be disabled for a
brief period 
of time.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.c
om
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

On Sep 18, 2006, at 9:17 AM, Darrick Hartman wrote:

> Marc G. Fournier wrote:
>> On Mon, 18 Sep 2006, David Morton wrote:
>>
>>> In my experience, postgres is slower.  Lately
there have been  
>>> reports
>>> of slowness from both databases concerning the
bayes database
>>> implementation, but throwing that issue aside,
I think I have seen
>>> mysql performing slightly better.
>>>
>>> Maia involves a lot of writes compared to
reads.  (Was was amazed  
>>> the
>>> other day watching iostat).  IIRC, Postgres is
slower on heavy
>>> writing. (and also needs the infamous vacumn
process)
>>>
>>> If anyone has a well tuned postgres server and
would like to counter
>>> this thought, feel free.   (And then
tell us how the heck to tune
>>> postgresql properly! )
>>
>> I'm running things on a PostgreSQL server, having
switched from MySQL
>> a little while back ...
>>
>> 0. make sure you run 8.1.x
>>
>> 1. give it lots of shared memory
>>
>> 2. make sure you run the autovacuum daemon
>>
>> At least, that's all the tuning I've done on her
... and its running
>> on a shared server with other processes running ...
>>
>> I switched from MySQL due to repeated database
corruption on the  
>> MySQL
>> side of things ... got tired of having to rebuild
it from scratch ...
> I've seen that as well.  My current install has some
issues with  
> innodb
> claiming that log sequence number bla bla is in the
future.  And  
> that my
> database may be corrupt.
> My thinking is that if I have mysql and postgres both
running on the
> box, I can leave email users and all sorts of web-based
tools in mysql
> and if I have corruption that would involve taking Maia
down in the
> future, I would not affect the majority of the
functions on this box.
> While an inconvenience, filtering could be disabled for
a brief period
> of time.

You could also run another instance of MySQL and an
alternate port  
just for Maia   Then you
have no issues learning a new db etc.

My .02 cents.


-Will
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users