drop-in-ability (was: RE: Re: [PATCHES] Select parser a t runtime )
От | Alex Avriette |
---|---|
Тема | drop-in-ability (was: RE: Re: [PATCHES] Select parser a t runtime ) |
Дата | |
Msg-id | 32BAF2A2B169D411A081009027464529019BD90A@ATD-NT5 обсуждение исходный текст |
Ответы |
Re: drop-in-ability (was: RE: Re: [PATCHES] Select parser a t runtime )
|
Список | pgsql-hackers |
I sent the list a message a little while ago about what I do with postgres. I thought, after all this discussion, that it might be important to send a further message to the list indicating why I chose not to use Oracle. I'm going to go out on a limb and say that I have one of the largest postgres databases in the world. At our site, we have quite a few oracle instances and something like 27 schemas (and, I'm afraid to report, a few Access as well). Our PG database dwarfs all the other databases combined. I chose postgres not because of any cost issue at all. The project that I am working on here is accustomed to spending $25,000 in a given week for new hardware, we bring on consultants as we need them et cetera. To me, what made postgres attractive was how simple it was to install and configure. Furthermore, I have had discussions with our oracle DBA's. When I mentioned I thought our number of rows could reach into the tens of millions, and the eventual storage estimate is something on the order of several terabytes, he told me I would need to hire on 2-3 fulltime DBA's if I wanted to use Oracle. My feeling on whether postgres is a "drop-in" replacement for Oracle is similarly simple. Any sufficiently competent programmer can make database-independant code. Up to this point, I have been working hard to make sure that, should higher management decide to use Oracle, I can use pg_dump and actually just move on over to Oracle. I would have chosen a similar approach if I had started with Oracle. Perhaps it is my background as a Perl programmer (it is the DataBase Independant driver, afterall), or perhaps it is my fear of change. But if you guys are concerned that one database is not a drop-in replacement for another, you are paying your programmers too much. I think perhaps it is the "Oracle Mentality" (or dare I say, Microsoft Mentality) to not worry about portability and compatibility that breeds this kind of programming and production. It is very much against, however, the opensource mentality. Dont beat yourself up, guys, over making postgres a drop-in replacement for Oracle. The people that would benefit from actually "dropping in" postgres into an Oracle install will have already eased the burden on themselves by being responsible in their database construction and programming. I haven't even been able to convince our Oracle guys that Postgres is actually a "real database" (its free?!! how can it be free?!). They would never, (ever!) consider dropping in postgres. If you're intent on taking "customers" from Oracle, catch them where youll be able to convert them -- before Oracle is even installed. alex
В списке pgsql-hackers по дате отправления: