| From: | Justin Clift <justin(at)postgresql(dot)org> |
|---|---|
| To: | veem v <veema0000(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Moving to Postgresql database |
| Date: | 2024-01-15 19:43:20 |
| Message-ID: | 0d732771804d0a62f84119c4e81deec9@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2024-01-15 14:16, veem v wrote:
> 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?
Is this the kind of thing you're looking for?
Regards and best wishes,
Justin Clift
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2024-01-15 20:00:10 | Re: Help needed for the resolution of memory leak |
| Previous Message | Joseph G | 2024-01-15 19:22:27 | Re: multiple missing providers from pgdg-common |