Moving to Postgresql database

From: veem v <veema0000(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Moving to Postgresql database
Date: 2024-01-15 04:16:47
Message-ID: CAB+=1TUyxXeRbmz6oRC+96EjLAnW7Qvqmse4iSNtWgH5i21mQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello Experts,
If some teams are well versed with the Oracle database architecture and its
optimizers working and designing applications on top of this. Now moving
same team to work on AWS aurora postgresql databases design/development
projects. Is any key design/architectural changes should the app
development team or the database design team, should really aware about, so
as to take right decision on any new development project in AWS aurora
postgresql database?
Or
Is there any list of differences(as compared to Oracle database) in key
concepts like for example basic design concepts, Normalization,
Partitioning, clustering, backup and recovery, Indexing strategy, isolation
level, performance which one should definitely be aware of?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message PavelTurk 2024-01-15 10:00:19 Add support for data change delta tables
Previous Message Yongtao Huang 2024-01-15 01:32:56 Re: Why scan all columns when we select distinct c1?