I'm working in a Java application with some colleagues and we are in
doubt wether to use Oracle or PostgreSQL as the data store. It will be a
OLTP mainly application.
Beside of license terms/costs which is a clear point in favor of
PostgreSQL, could you please help me to get some more details regarding
what you can do in PostgreSQL and you can't in Oracle oand viceversa,
and what can be done using both but it is better done by PostgreSQL vs
Oracle and so on?
I mean, about functionalities, performance, support costs if any and
st 20. 5. 2020 v 9:34 odesílatel Alfonso <[hidden email]> napsal:
this analyse can have more than thousand pages. Oracle and Postgres are two different databases (in some parts - ACID implementation, planner, plan cache, architecture it is very different).
Probably a distance between Oracle and Postgres is much less than Oracle and MSSQL database, but that is all what can be reply on too general question.
You can read some notes related to migration from Oracle to Postgres. More it depends how deep are you SQL and database knowledges. For some low levels (lot of developers has less than minimum knowledges about databases) the the difference is very small. On high levels almost all is different (in details). It is hard to say if some is better or worse, or is better to do something on Postgres and better to do something on Oracle - because these databases are different and has different sensitivity on patterns and antipatterns.
Very different is maintenance of these databases. Postgres is simply database with low necessity of maintenance (sure, that depends on dimensions and risks). Oracle is much more complex difficult to learn system. But for Oracle there is lot of commercial (not cheap tools) and generally Oracle is better adapted in enterprise area (special hw, tools, legislative).
So in detail - almost all are different, but both these databases are relational SQL databases.
In reply to this post by Alfonso
With massive development within OSS PosgreSQL over the years, there is plenty of things it can do when compared to Oracle. The below URLs give you a comprehensive comparison table, I am sure you or your colleagues may have already stumbled upon these URLs. In addition to that, there is something called "oracle compabilities" for PostgreSQL which makes it more like Oracle for most of the Oracle's native functionalities like packages and procedures etc.
From: Alfonso <[hidden email]>
Sent: Wednesday, 20 May 2020 7:56 AM
To: [hidden email]
Subject: Q: Comparing PostgreSQL and Oracle
I'm working in a Java application with some colleagues and we are in doubt wether to use Oracle or PostgreSQL as the data store. It will be a OLTP mainly application.
Beside of license terms/costs which is a clear point in favor of PostgreSQL, could you please help me to get some more details regarding what you can do in PostgreSQL and you can't in Oracle oand viceversa, and what can be done using both but it is better done by PostgreSQL vs Oracle and so on?
I mean, about functionalities, performance, support costs if any and qualtity, etc.
IMPORTANT NOTE: Fuji Xerox email transmission, including any attachments, is private and confidential and may contain legally privileged information. It is for the addressee's attention only. If you are not the intended recipient and have received this transmission, you must not use, edit, print, copy or disclose its contents to any person or disseminate the information contained herein or hereto attached, and you must notify sender immediately by return email and delete this transmission from your system. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. We have used reasonable efforts to protect this transmission from computer viruses and other malicious software, but no warranty is made and the sender takes no responsibility for any loss or damage incurred from using this email or the information contained in this email.
For what it's worth, I used Oracle daily as a DBA and developer for my job from 1983 until around 3 years ago when Postgres was chosen for a project I was assigned to. I became pretty familiar with the workings of Oracle and was somewhat skeptical when told we would be using Postgres, however it has honestly been like a breath of fresh air. It has all the transactional behaviour of a 'proper' RDBMS (even transactional DDL which as far as I'm aware is still not supported in Oracle), and has all the features a developer actually cares about. Postgres runs beautifully either locally on a laptop, or in a Docker container using a tiny fraction of the resources Oracle would need to do the same thing, so makes true local full-stack development a delight. As someone familiar with both, I can honestly say go with Postgres. You won't regret it.
On Wed, May 20, 2020 at 6:08 PM Ahmed, Nawaz (Fuji Xerox Australia) <[hidden email]> wrote:
In reply to this post by Alfonso
On Wed, May 20, 2020 at 12:34 AM Alfonso <[hidden email]> wrote:
Perhaps it is better to do the inverse: Think about what do you need to do. DB Size (in hundred of Gb). How heavy will be the use of the database. Concurrent users. The peak number of users. How many batch operations. Size of those batch operations. etc
And based on that compare what functionality Oracle and Postgres offer to you.
|Free forum by Nabble||Edit this page|