1 |
About this topic, I want to know if postgresql may be a good choice |
2 |
instead of mysql. |
3 |
explain my case, I have a website with a intranet/extranet that uses |
4 |
postgresql as DB to stock a lot of data. Both of they will need to |
5 |
query a users table in DB to authenticate the users. |
6 |
What I want is to make just one users DB which one I can use to |
7 |
authenticate my web users, my email accounts (postfix + courier), the |
8 |
workstation login (linux workstations) and some samba clients. |
9 |
Considering that my website already use PostgreSQL, the development |
10 |
guys ask me about keep using only PostgreSQL. I think it could be a |
11 |
good idea since they will not have to change they sqls (mysql doesn't |
12 |
have support to all the things they commonly use) but I know postgre |
13 |
may be a bit slower then mysql and also a bit heavier. |
14 |
Did somebody have any experience of these type of authentication with postgres? |
15 |
Could the perfomance differences be meaningless? Or maybe it's better |
16 |
to do the effort to exchange the users DB to mysql? |
17 |
Note1: I already authenticate my email accounts with courier + mysql. |
18 |
Note2: In both ways I will use a separated server to run the DB. |
19 |
|
20 |
Tks in advice, |
21 |
|
22 |
Claudinei Matos |
23 |
|
24 |
> That being said, with today's hardware, unless you are expecting a lot of |
25 |
> traffic, either one will do. Unless under load, mysql will respond in |
26 |
> milliseconds. However, if load is a concern, OpenLDAP might save you on |
27 |
> hardware costs (don't have to buy as many servers), and it will not add |
28 |
> any latency to you web transactions. But mysql is probably easier to |
29 |
> manage, especially if you already know SQL. |
30 |
> |
31 |
> -Eric |
32 |
> |
33 |
> -- |
34 |
> arctic bears - email and dns services |
35 |
> http://www.arcticbears.com |
36 |
> |
37 |
> -- |
38 |
> gentoo-server@g.o mailing list |
39 |
> |
40 |
> |
41 |
|
42 |
-- |
43 |
gentoo-server@g.o mailing list |