HI I think it boils down to the product that you really know and is used to.
I'm for example, is working at a telco where we prefer oracle, it is expensive yes, but it fullfills our needs of functionality, scalability and performance as well as we (internally) know the product very good. I think the same goes for mysql/postgresql, which product you're using is (for a major company) not that interesting but the benefits/costs are. That means does the product deliver what's needed and does their support really jump to our needs and problems? That's the basic problem we got, Oracle do, are not open source, and not free in terms of cost...... MySql and PostgrSQL are not free when it boils down to 24x7 support either..... It's all about business, what it's worth to you, and what you can afford... Personally by the way, I'm using mysql..... basic stuff, really don't know the cores of it --Robert On Thu 26 May 2005 06.36, kashani wrote: > Claudinei Matos wrote: > > 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. > > Break that into paragraphs next time, it's a little hard to parse. > > The performance difference between Mysql and Postgres is going to be > pretty negligible assuming we're not talking about a gigantic number of > user data. The tables will fit into RAM nicely and your selects are > going to be quick in either db. > > I would not recommend running Mysql and Postgres on the same server if > you're doing any sort of real traffic. Real traffic being highly > subjective to your workload, software, data size, and hardware. In my > environment I found that Mysql and Postgres on the same server > backend-ing some fairly heavy web sites cut performance to 60-70% of > what I'd see on the purely Mysql servers. Your mileage will vary greatly. > > In your case I'd break out a spread sheet and start comparing which > database your authentication software requires or supports. Assuming > both are equally supported I'd go with the db you're more comfortable > administrating. The amount of SQL either Mysql or Postgres supports is > not likely to play a part in your decision. > > Now I move into purely editorial mode > > Mysql and Postgres admins, developers, fans, etc come from two > different worlds. People who know what they are doing in Postgres seldom > know what they are doing on Mysql. And vice versa. Getting anyone who is > comfortable with their db platform to switch will be painful and is > going to require a mandate from on high. And someone who really knows > the new database is going to have double check code, db schema, > indexing, etc etc for the next 6 months. Because everyone is going to do > all the things that work in the old database that you should never, ever > do in the new database. And then complain about the new platform, loudly. > > I'm enforcing such a move this month and already hate every idiot > developer who was a fan of the old database platform who are thankfully > in the minority. I don't suggest doing such a move unless you have to. :( > > kashani -- [email protected] mailing list
