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 1x5oxe-000IOJ-2d for pgsql-admin@arkaria.postgresql.org; Sun, 13 Sep 2026 18:29:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1x5oxe-00AExg-1H for pgsql-admin@arkaria.postgresql.org; Sun, 13 Sep 2026 18:29:54 +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 1x5owa-00ADOI-0l for pgsql-admin@lists.postgresql.org; Sun, 13 Sep 2026 18:28:48 +0000 Received: from cc-smtpout2.netcologne.de ([2001:4dd0:100:1062:25:2:0:2]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x5owW-00000000EdD-1BN4 for pgsql-admin@lists.postgresql.org; Sun, 13 Sep 2026 18:28:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1789324119; bh=dO+fwaesXwy+0zswMf1uBzFvx+H4zl6bEZh0uYEUdRo=; h=Date:From:To:Subject:In-Reply-To:References:Message-ID:From; b=p0eWeX2mG8mlNPoDCnjBmhaCtN+9YrXnUIsDTwUYCM+vyyOrZ66gZzyslwcmNj7A5 vLSJVA90vIOg+uIgfhkU4IedutrPRLqJbjjy8Wr3wr61SnLyImxDitLGJOdY2lBeNT lzgqXUOEKAY06VcQjeZZOyXOUYB3iB+g9wQm6FMPkE1EMznKjgtU8WpQnZ5YeI4V+o Xi9b6EcHUR41rTuuZ3oEKrNvBMfhkkxonosYZKdFJJG9YYjpxZG70H0y86itgbj63Z kaZeNHkdEV3Yo5/3lZz1abRwEE2Z9tmwEbYpeD/LJYt0FKhyga/xGa/JZ7yz3MkzoT HyEV7qYYXswww== Received: from cc-rc3.netcologne.de (cc-rc3.netcologne.de [89.1.9.223]) by cc-smtpout2.netcologne.de (Postfix) with ESMTP id 5BF9811D82 for ; Sun, 13 Sep 2026 20:28:39 +0200 (CEST) Received: from cc-rc3.netcologne.de (localhost [127.0.0.1]) by cc-rc3.netcologne.de (Postfix) with ESMTPA id 3E8A22015A for ; Sun, 13 Sep 2026 20:28:39 +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:28:39 +0000 MIME-Version: 1.0 X-Originating-IP: 2a03:b580:af79:ce01:cecb:930d:1d29:4682 Date: Sun, 13 Sep 2026 20:28:39 +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="=_2eb3c213211ec814c341e84cf1d54606" X-NetCologne-Spam: L List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=_2eb3c213211ec814c341e84cf1d54606 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed 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. --=_2eb3c213211ec814c341e84cf1d54606 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

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/cloudna= tive-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.

--=_2eb3c213211ec814c341e84cf1d54606--