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 1ujs8H-00D0Xp-EF for pgsql-general@arkaria.postgresql.org; Thu, 07 Aug 2025 04:21:37 +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 1ujs8F-002aTC-1S for pgsql-general@arkaria.postgresql.org; Thu, 07 Aug 2025 04:21:35 +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 1ujs8E-002aSw-Mw for pgsql-general@lists.postgresql.org; Thu, 07 Aug 2025 04:21:34 +0000 Received: from mail-ed1-x52d.google.com ([2a00:1450:4864:20::52d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ujs8B-0019oS-2S for pgsql-general@lists.postgresql.org; Thu, 07 Aug 2025 04:21:33 +0000 Received: by mail-ed1-x52d.google.com with SMTP id 4fb4d7f45d1cf-604bff84741so1064884a12.2 for ; Wed, 06 Aug 2025 21:21:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1754540491; x=1755145291; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=NP4/NWvBa5qf99XfE3DDvhgyzKQUrKMYOUIGTb3akPI=; b=HzyskmnLnjnluIvu7Sh8WczHx/BoyNRFmtmXRAvNpsnz1wIhfJOuxXVnscbnClIFKt 7yhN7/MGAIrqybanefDL1WzSQc/VJicTA0+7+kzveHr1ozXV+as9eCIZLxoFvkjp6uhe 8zsww5pQgLEmaQuqirIjF+vTjZ6bRgNtGIJzPr5/gX8+E+zOSOPXUpcQ12yOe6v6C6y2 nXHqLBq8dxxzet1zhs/79Fy1fuJpDiAYdye9qSZ+FNTo0eCH9GQTZEVloGKNJwLbcirL WWQAWjzmPWD9DnwR7gT/oNfGlcIr+7WGHWYqovnEdxQKltrmPJN3mIXtkOy9A4Tb6ulK o3zw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754540491; x=1755145291; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=NP4/NWvBa5qf99XfE3DDvhgyzKQUrKMYOUIGTb3akPI=; b=vriNZ2DTO5HM/08QnRljcUpifeOBx17ucsVQ4W+SOuQnFpYCN0+UCMAPWATin3GPrA DxRw7MXd7+p8eMkH0yUN6EjBGKEMNqBkTk+sYj4PLqJAc6XyeFNbr0ctY8A96o9ljsz9 R+5wex9VP9BB63CIZrz7jXONDIHf9vnbNGucDJ17RwRyCiVBHVcpijT07fDViCqcbVDp sW3ezDgag65wdjt+sdKTrL0SlfelCN7r54Q8JujYJs20ZQO6EB/C26rtOe3HT+0M8RI1 QnW9iF4rZpmcAuJlOJrT1drj7ijJ/cQ3bwsa9ADoxXu3ryoFwaGI/1aOMAG4cbtPMmwz 6S7A== X-Gm-Message-State: AOJu0YxbOvn8s0mZkzaAGgIuA8cz0g11reC3oX+tVRPMFAOR1qSFEHfT J9VcWbUSZetvHtFCAeGoIONtsYSPo+q+8VL5RekE5NULsk5pDNn1bJKvK3K64se7K/5+ct/RcT1 jXV8QwKPqifU9DcClid8BiVdiLEm9Wl8= X-Gm-Gg: ASbGncv9fAJM6r6mEcF6T/iEkzB4Czp6XryaThEG7k/RrOZk00WuzH+y50laZG/hrAh Rr3AXjP42yb+W/GCU9aAkouaQEdLBmlBUj+6H8R1ER90DcMIUKU3FvM/QEWHC1gNXsnu2wbxSpg b5SoMdFrswCxhpy8/NC3dxON9uciTmr/wZj9UWcq3waowy0p5qbo1/s35qO7AxBquFMBs/ott6n fCaQWEJ X-Google-Smtp-Source: AGHT+IFFQ1lMo2v+rkVgXkgxZhMvxt+0+kRoTMj6Ji8aJQZfHRmmLijBsrZvYBa5KATbMPt5U+kz3KciY0uqKQK2+vk= X-Received: by 2002:a05:6402:4312:b0:615:9b4e:7b93 with SMTP id 4fb4d7f45d1cf-617961f1bebmr4554120a12.30.1754540490832; Wed, 06 Aug 2025 21:21:30 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Siraj G Date: Thu, 7 Aug 2025 09:51:18 +0530 X-Gm-Features: Ac12FXyOk6tOODn9-ar4oMFAdmsPOqv1N_H0fyoJ60jZJVRkf_ok7Uk1ep1WDNQ Message-ID: Subject: Re: Approach for DB migration To: Ron Johnson Cc: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000b3415a063bbeca64" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b3415a063bbeca64 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Yes Ron, database migration service. But it works better if we have to migrate all the DBs in one shot since it converts the target DB into a read replica during the migration. Regards Siraj On Thu, Aug 7, 2025 at 9:33=E2=80=AFAM Ron Johnson wrote: > On Wed, Aug 6, 2025 at 9:30=E2=80=AFPM Siraj G wrot= e: > >> Hello Experts! >> >> I have this environment with 100+ DBs and would like to migrate to GCP's >> cloud SQL for Postgres. >> >> Primary: 48 CPUs, 48GB memory >> Secondary/Read Replica: 80 CPUs, 128GB memory >> PG version: 12.22 (we have already started the upgrade process) >> OS: Ubuntu >> >> I would like to migrate 2 DBs first and a few more later. I was thinking >> of logical replication, but wanted to take recommendations if there are >> better approaches available. We cannot afford breaking the read replica = due >> to our read intensive app connects to this node. >> > > GCP haa a migration service. Have you investigated it? > > -- > Death to , and butter sauce. > Don't boil me, I'm still alive. > lobster! > --000000000000b3415a063bbeca64 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes Ron, database migration service. But it works better i= f we have to migrate all the DBs in one shot since it converts the target D= B into a read replica during the migration.

Regards
Siraj

On Thu, Aug 7, 2025 at 9:33=E2=80=AF= AM Ron Johnson <ronljohnsonjr= @gmail.com> wrote:
On Wed, Aug 6, 2025 at 9:30=E2= =80=AFPM Siraj G <tosiraj.g@gmail.com> wrote:
Hello Experts= !

I have this environment with 100+ DBs and would li= ke to migrate to GCP's cloud SQL for Postgres.=C2=A0

Primary: 48 CPUs, 48GB memory
Secondary/Read Replica:= 80 CPUs, 128GB memory
PG version: 12.22 (we have already started= the upgrade process)
OS: Ubuntu

I= would like to migrate 2 DBs first and a few more later. I was thinking of = logical replication, but wanted to take recommendations if there are better= approaches available. We cannot afford breaking the read replica due to ou= r read intensive app connects to this node.
GCP haa a migration service.=C2=A0 Have you i= nvestigated it?

= --
D= eath to <Redacted>, and butter sauce.
Don't boil me, I'm = still alive.
<Redacted> lobster!
=
--000000000000b3415a063bbeca64--