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.96) (envelope-from ) id 1x5pCA-000IWq-0f for pgsql-admin@arkaria.postgresql.org; Sun, 13 Sep 2026 18:44:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1x5pC9-00AN3e-2F for pgsql-admin@arkaria.postgresql.org; Sun, 13 Sep 2026 18:44:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1x5pC9-00AN3W-1D for pgsql-admin@lists.postgresql.org; Sun, 13 Sep 2026 18:44:53 +0000 Received: from cc-smtpout1.netcologne.de ([2001:4dd0:100:1062:25:2:0:1]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x5pC5-00000000EoA-2KU7 for pgsql-admin@lists.postgresql.org; Sun, 13 Sep 2026 18:44:52 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1789325089; bh=Aw0I1VA7DPNiu1i+17VFowRnf/aI+H+nANv0XJQRoMI=; h=Date:From:To:Subject:In-Reply-To:References:Message-ID:From; b=eAbbStJVM3vZdokkRu7VeAmWVKKi5RrvEbG4Mk/Gks0Pvev4aNiKI/Q3WaE/o/KUB Eo33a/m5rHN9i1P8zpm/Ty1zkUFI+TB73mmYk47yc2fbOa0de0osAjbU1ZV3rmq8x6 ijDR5C9uhfnbONr6KRw2BlHkANBzAYwSd+UIMwCgW2YxFlMzhlqRgL2okXdJNU5v73 90MSu4eFistwtvk9n/7MXQrObtlRJ8nauXPxnC0GE6sUJWVGzONkZFowSSSEmIP544 ogkS06AjZrupTmQuPMIQeSPcvka1EdBK8DEhkzOh32k1zj4aCiMLmnw2NAzK8bkYCt 7lCN/laThUzkQ== Received: from cc-rc3.netcologne.de (cc-rc3.netcologne.de [89.1.9.223]) by cc-smtpout1.netcologne.de (Postfix) with ESMTP id D717812316 for ; Sun, 13 Sep 2026 20:44:49 +0200 (CEST) Received: from cc-rc3.netcologne.de (localhost [127.0.0.1]) by cc-rc3.netcologne.de (Postfix) with ESMTPA id AD3591FF35 for ; Sun, 13 Sep 2026 20:44:49 +0200 (CEST) Received: from 2a03:b580:af79:ce01:cecb:930d:1d29:4682 via cc-webproxy1.netcologne.de ([89.1.8.191]) by cc-rc3.netcologne.de with HTTP (HTTP/1.1 POST); Sun, 13 Sep 2026 18:44:49 +0000 MIME-Version: 1.0 X-Originating-IP: 2a03:b580:af79:ce01:cecb:930d:1d29:4682 Date: Sun, 13 Sep 2026 20:44:49 +0200 From: gunnar wagner To: pgsql-admin@lists.postgresql.org Subject: Re: Migration from crunchy postgres to CNPG In-Reply-To: References: Message-ID: X-Sender: vrms@netcologne.de Content-Type: multipart/alternative; boundary="=_eb3038047bd00a3847abdfa96b672b41" X-NetCologne-Spam: L List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=_eb3038047bd00a3847abdfa96b672b41 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On 2026-09-13 20:28, gunnar wagner wrote: > On 2026-09-13 12:18, Raj wrote: > >> Hi all, we are using crunchy data postgres in OPENSHIFT and already >> decided to migrate to EDB postgres CNPG. >> Do we get any support from EDB to deploy it in OPENSHIFT or is it on >> our own? Anybody working in EDB CNPG postgres in openshift ? >> Is it similar to crunchy postgres? > > I'd say those are questions for EDB, who, as being the main force > behind OpenSource CNPG, might offer support (contracts). > > I would expect that CNPG postgres behaves quite like vanilla-opensource > postgres (because I believe that is what is doing the actual work) to > the application. I am sure that there is quite a learning curve to > mastering operations especially if you come from VM or bare-metal based > installations though. > > https://github.com/cloudnative-pg might be a good starting point for > further investigations into the topic. It has i.e. a link to a Slack > space, where you probably find the right audience. this also looks like a good starting point to get one's feet wet with the matter https://github.com/cloudnative-pg/cnpg-playground --=_eb3038047bd00a3847abdfa96b672b41 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

On 2026-09-13 20:28, gunnar wagner wrote:

On 2026-09-13 12:18, Raj wrote:

Hi all, we are using crunchy data postgres in OPENSHIFT a= nd already decided to migrate to EDB postgres CNPG.
Do we get any support from EDB to deploy it in OPENSHIFT = or is it on our own? Anybody working in EDB CNPG postgres in openshift ?
Is it similar to crunchy postgres? 

I'd say those are questions for EDB, who, as being the main force behind= OpenSource CNPG, might offer support (contracts).

I would expect that CNPG postgres behaves quite like vanilla-opensource = postgres (because I believe that is what is doing the actual work) to the a= pplication. I am sure that there is quite a learning curve to mastering ope= rations especially if you come from VM or bare-metal based installations th= ough.

https://github.com/cloudnative-pg might be a good s= tarting point for further investigations into the topic. It has i.e. a link= to a Slack space, where you probably find the right audience.

this also looks like a good starting point to get one's feet wet with th= e matter http= s://github.com/cloudnative-pg/cnpg-playground


--=_eb3038047bd00a3847abdfa96b672b41--