Data Migration Blogs
Why aren't more people/companies using PostgreSQL?
- Font size: Larger Smaller
- Hits: 1509
- 11 Comments
- Subscribe to this entry
- Bookmark
Why aren't more people/companies using PostgreSQL? Why aren't they moving from proprietary databases to PostgreSQL?
Possible answers: I haven't heard of PostgreSQL. I don't think PostgreSQL will meet my needs. I don't know how to get away from my database vendor.
I'd like to hear some of the reasons for not considering PostgreSQL when creating or migrating a database.
Comments
-
Thursday, 25 October 2012The /management/ have not heard of PostgreSQL. Does it come with commercial support? Who is EnterpriseDB and Command Prompt? My CEO friends haven't heard of them. It's better stick with Oracle / IBM / Microsoft.
-
Thursday, 25 October 2012
1) partitioning is a joke - slow inserts, every partition has to be created manually 2) no query progress - is it waiting on something? is it reading from disk? 3) not full SQL:2003 support for window functions
-
Thursday, 25 October 2012
I think PostgreSQL need some to feature to attract people. Like: 1. Proper declarative syntax for table partitioning in CREATE TABLE 2. DDL triggers 3. Support for configuring async/sync steaming replication as well as log shipping warm/hot standby through pgAdmin 4. Official Command line and GUI (through pgAdmin) for data backup with incremental/delta backup 5. Integrated pg_rman support 6. Support for ROLLUP/CUBE clause in SQL Select statement 7. Updatable views 8. SQL Proxy and query analyzer
-
Thursday, 25 October 2012
I'm not maybe someone who has experience with PGSQL, but i'm missing some good development tool (no, notepad doesn't fit here). pgadmin is good for running queries already developed... just my two cents.
-
Thursday, 25 October 2012
Me too! We run a big ERP system here (Banner) and I think your reasons listed above apply. The biggest show-stopper imo at this time is the large # of oracle forms. That and inertia, but I'm working on it. Sure would like to know what might work.
-
Thursday, 25 October 2012
There are some tools available, for the translation of Oracle Forms to Java and the Oracle Stored Procedures (PL/SQL) to Postgres functions (PL/pgSQL) so at least that removes some of the headaches of migrating an Enterprise level database to Posgresql.
-
Thursday, 25 October 2012
PG remains neither Fish (MySql) nor Fowl (Oracle/DB2/SS). The Fish is a simple minded SQL datastore for non-mission critical web projects, while Fowl are the mission critical GL based applications that can only be trusted to Big Corp Software. PG has long yearned to be Fowl, but seems to be embracing a Fish-y next life.
-
Thursday, 25 October 2012
In my case, the feature that make us choose Mysql was the multi-az that amazon can give you when you are using a RDS.
-
Thursday, 25 October 2012
We see quite a few users who would love to switch to Postgres from MySQL but are afraid of breakage to their application. The lack of a well documented and understood migration process is a major liability. There are a few specific features Postgres lacks as well, possibly the most significant being UPSERT/MERGE behaviour.
-
Tuesday, 18 December 2012
In Spain, the most important problem is with Consultors. You contract an external consultor to look for the technology you really need for your company, but, the reality is that the consultor company is a Microsoft reseller and no matter which is your problem, the solution is always Sql Server.
The three most common reasons I run across: 1) Under marketed. 2) MySQL has an undeserved reputation for being fast. 3) Off-the-street skill set. PHP left the software industry laden with MySQL familiarity. #1 and #3 are getting better very quickly. #2 is just funny when you switch your app from Pg to MySQL (rarely is MySQL faster than PostgreSQL). "But I thought MySQL was..." "Yeah, you thought, and you thought wrong."