Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rPSrp-00Bm2g-3g for pgsql-general@arkaria.postgresql.org; Mon, 15 Jan 2024 19:43:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rPSro-00H7ms-7x for pgsql-general@arkaria.postgresql.org; Mon, 15 Jan 2024 19:43:28 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rPSrn-00H7mi-T5 for pgsql-general@lists.postgresql.org; Mon, 15 Jan 2024 19:43:27 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rPSrl-001hCA-4D for pgsql-general@lists.postgresql.org; Mon, 15 Jan 2024 19:43:26 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:MIME-Version:Sender :Reply-To:Content-ID:Content-Description; bh=8qFOix+w9l8MOgtyE6RV4dycR9pPur+E6a7Q7AlGMAU=; b=u/Q6DcLtQb37uZaTxNHp6xMzVB KfO2of33EnOO3Q4VU9oVMFdFLtDzWbUz4BHBuqPAI469bATJS2BMJNv5Pb5P9rwQcvPv5wA449utP OvjlgJAta0B8W9naweQIWUCmtyvTjbFh7VFbALIQN55hbvD3wCbh+Mi1tWBQ5h9aBmajDJBfYgc2x D8+hh/wURtrzbNPtI/O58y/7Yx7BIzJApbvTb4Q5YVHIuXueai23e0x0oflNINrdsW4i1cMQo+j/R p+3GTOw9yKVyR5hHNh8oVTHyAGd7/A5Y6MOp8tTOmqPEU4cLa8PM3YyKJp9+LfJxr9i7H5ymjNmGv hB7jANPw==; Received: from meldrar.postgresql.org ([87.238.57.231] helo=webmail.postgresql.org) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rPSrg-004bmI-4i; Mon, 15 Jan 2024 19:43:23 +0000 MIME-Version: 1.0 Date: Tue, 16 Jan 2024 05:43:20 +1000 From: Justin Clift To: veem v Cc: pgsql-general Subject: Re: Moving to Postgresql database In-Reply-To: References: User-Agent: Roundcube Webmail/1.4.15 Message-ID: <0d732771804d0a62f84119c4e81deec9@postgresql.org> X-Sender: justin@postgresql.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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? https://www.enterprisedb.com/blog/the-complete-oracle-to-postgresql-migration-guide-tutorial-move-convert-database-oracle-alternative Regards and best wishes, Justin Clift