About this topic, I want to know if postgresql may be a good choice
instead of mysql.
explain my case, I have a website with a intranet/extranet that uses
postgresql as DB to stock a lot of data. Both of they will need to
query a users table in DB to authenticate the users.
What I want is to make just one users DB which one I can use to
authenticate my web users, my email accounts (postfix + courier), the
workstation login (linux workstations) and some samba clients.
Considering that my website already use PostgreSQL, the development
guys ask me about keep using only PostgreSQL. I think it could be a
good idea since they will not have to change they sqls (mysql doesn't
have support to all the things they commonly use) but I know postgre
may be a bit slower then mysql and also a bit heavier.
Did somebody have any experience of these type of authentication with postgres?
Could the perfomance differences be meaningless? Or maybe it's better
to do the effort to exchange the users DB to mysql?
Note1: I already authenticate my email accounts with courier + mysql.
Note2: In both ways I will use a separated server to run the DB.

Tks in advice,

Claudinei Matos

> That being said, with today's hardware, unless you are expecting a lot of
> traffic, either one will do. Unless under load, mysql will respond in
> milliseconds. However, if load is a concern, OpenLDAP might save you on
> hardware costs (don't have to buy as many servers), and it will not add
> any latency to you web transactions. But mysql is probably easier to
> manage, especially if you already know SQL.
> 
> -Eric
> 
> --
> arctic bears - email and dns services
> http://www.arcticbears.com
> 
> --
> gentoo-server@g.o mailing list
> 
>

-- 
gentoo-server@g.o mailing list