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 1qfOWM-00Ao2V-6f for pgsql-sql@arkaria.postgresql.org; Sun, 10 Sep 2023 17:46:54 +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 1qfOWL-00B0oQ-4H for pgsql-sql@arkaria.postgresql.org; Sun, 10 Sep 2023 17:46:52 +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 1qfOT7-00AsYP-Ml for pgsql-sql@lists.postgresql.org; Sun, 10 Sep 2023 17:43:33 +0000 Received: from mail-vs1-xe30.google.com ([2607:f8b0:4864:20::e30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qfOT4-003ot7-Aq for pgsql-sql@lists.postgresql.org; Sun, 10 Sep 2023 17:43:32 +0000 Received: by mail-vs1-xe30.google.com with SMTP id ada2fe7eead31-44ee3a547adso1408912137.2 for ; Sun, 10 Sep 2023 10:43:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694367809; x=1694972609; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=MpyoLT4BNwxxDyZtk1UIKOAotD4g09Xl6jgqZcCaGeI=; b=XWHKTXRw9SeGIx40unbXRw0hYU1LW4fcDvhAmrX8wwHg8gtCttN4eCMiMmD5/yFOci Ze2tim+w2rrxCTC2jbmyfLL9RvQULv7sGkx1ZlhvkvY8o/U19JittdALCgvIOx0MeraY IlRAgOq1vMWC8roK2Sv1HKJazNK+o1hLMm9eXwgfiPuCGeRDhR1tEkHWvNM5D8a+WLU6 P47IqHkfZ6Nn3kny+14IkGzEH1vG5Igburw+g1uha/h/8QRwn/r+euS37PZryQDwJfAn oIOheBvCnq3YJFCdkp+RgUQo66Y2d+EYisiKLy7v3m0kBfLg/FRqaXW6hqqqFypks8YL AJYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694367809; x=1694972609; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=MpyoLT4BNwxxDyZtk1UIKOAotD4g09Xl6jgqZcCaGeI=; b=uqPYISp/D6yG4qjRKNFbrjTfMQ7e7Yxbitczt+mhHcJriPC8EyMvnyymnBm60wOuOM 4o/ZkyTlSHQf6Gpy34xlEH+zBC03hBV3qceJTpiAZ0TLBCZEPqA18DLNyf/WzPB+UBut FddQtMOtybi4W4uSKWjvvmswtfmPccwpx2VHrKKAxaZe6m0cufrO035iFmrhkHegJIB8 nhZYhASV5OPpYCk6aCRNw+SFmt4rLfpnvdtsws5n7PloMvHNaE2BGj+dAIVFo1WYM/x3 kJN5Ry5EumS4x34MKjhg39+xhoOoJXXEXDC8SOcXgxsQ5up7RNORhUsaIQhsb8+Xy15x jFdQ== X-Gm-Message-State: AOJu0Yy14exXsQAvH+mDD263iwhAyI+gpOLISRxbnTKrF0VStBx206+/ hX6v2O+J8rt8cYZWHqTClBgZMHAuu+cspfq5lgs4wtwVnho= X-Google-Smtp-Source: AGHT+IFXemD8vSaw9GPOqqo6iqWvmNG1pLQHugHn9DcEgy5QYUEKAUorm2XVoP+FDBooF6zduilOcMV4vAX2MtKVaIU= X-Received: by 2002:a05:6102:1c1:b0:44d:634c:1125 with SMTP id s1-20020a05610201c100b0044d634c1125mr6987720vsq.13.1694367809264; Sun, 10 Sep 2023 10:43:29 -0700 (PDT) MIME-Version: 1.0 From: kunwar singh Date: Sun, 10 Sep 2023 13:43:18 -0400 Message-ID: Subject: How to handle application connectivity change when moving from Oracle to Postgres in GCP To: pgsql-sql@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000063e0eb060504bf71" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000063e0eb060504bf71 Content-Type: text/plain; charset="UTF-8" Hi Listers, Say we have this App->DB connectivity Model. APP1 Contains synonyms which point to objects under APP1. APPOWN Contains the tables, indexes And it is a Java application that connects to APP1. Now when the database is switched from Oracle 19c onprem to CloudSQL Postgres say v15. Questions that I have: 1. What needs to be done at the database end in terms of schema setup in order to ensure the application is able to connect to the relevant tables without any concerns? 2. Do I need to create users APP1 and APPOWN in postgres? If so, what privileges are required to be assigned to these? 3. How to tie them with service accounts? 4. With which username/service account does the application make connection to the database? I still don't understand user/schema concepts in postgres tbh as I'm still a noob :) -- Cheers, Kunwar --00000000000063e0eb060504bf71 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Listers,

<= /div>
Say we have this=C2=A0App->DB connectivity Model.
APP1
Contains synonyms which point=C2=A0to objects u= nder APP1.

APPOWN
Contains the tables, i= ndexes

And it is a Java application that connects = to APP1.

Now when the database is switched from Or= acle 19c onprem to CloudSQL Postgres say v15.
Questions that I ha= ve:

1. What needs to be done at the database end i= n terms of schema setup in order to ensure the application is able to conne= ct to the relevant tables without any concerns?=C2=A0
2. Do I nee= d to create users APP1 and APPOWN=C2=A0in postgres? If so, what privileges = are required to be assigned to these?
3. How to tie them with ser= vice accounts?
4. With which username/service account does the ap= plication make=C2=A0 connection to the database?

I= still don't understand user/schema=C2=A0concepts in postgres tbh as I&= #39;m still=C2=A0a=C2=A0noob :)=C2=A0



--
Cheers,<= br>Kunwar
--00000000000063e0eb060504bf71--