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 1sgEsn-00HBOg-C3 for pgsql-admin@arkaria.postgresql.org; Tue, 20 Aug 2024 02:46:05 +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 1sgEsj-006rFx-U5 for pgsql-admin@arkaria.postgresql.org; Tue, 20 Aug 2024 02:46:02 +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 1sgEsj-006rEv-Ef for pgsql-admin@lists.postgresql.org; Tue, 20 Aug 2024 02:46:02 +0000 Received: from mail-oo1-xc29.google.com ([2607:f8b0:4864:20::c29]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sgEsh-000V0f-6C for pgsql-admin@lists.postgresql.org; Tue, 20 Aug 2024 02:46:00 +0000 Received: by mail-oo1-xc29.google.com with SMTP id 006d021491bc7-5d82eb2c4feso3305943eaf.2 for ; Mon, 19 Aug 2024 19:45:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724121957; x=1724726757; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=iOQa+h9d40R1zroblT+AUo5NhAQILaREMbVTaiS/rnA=; b=B1+MFV9kMwAXOes537xSyZngb1VBVhwFr8zso+K34K+xNvyF2OskoWA0xW3kE0+dTV IsLr4OR6xTAvwhXa4C25hNjwC+i/K1OhMLot4FZBAuDdShHukyivG9dXM2ZiJh7Kf121 uxWP1xp6AzbA17bDI6dgn1e2+h2YYQ/gEt1bK8cwPTQrKBLzj3RU1RLorp0AA05IoIBY JmQHZSx3klkrn4gV6jQnq2CHXPhcesteZOQ488A7jrfTE74YwqRhpfiiNLcCgDE373U0 HlL6AIjXDXLXQCFNfDLp5/XB6fHnjpsq36H6b62EHvtuNaODzlSzK0+rW7EZWDnGRD92 Zqeg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724121957; x=1724726757; h=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=iOQa+h9d40R1zroblT+AUo5NhAQILaREMbVTaiS/rnA=; b=HovnXUtJ+K0AuNouvOTuIO8Ft63AJsRlEag3BUc4z5VN75VPuWOGoaYkPwSH2VtzN3 xHM0iU+/PJ5WMBwgT4CtKTqz5/pny/DVdIs8riMzdotTz2V1LFMUc0Kqk2ivOHXmRS3L KuK2+2HE98pMQIU2Zb54v1aF7gTtpcMdRFBtzWyrEsI1OtPc3BacmeBIYIRnUIzfH4cS qdtTExfib2p9V4l9VNukT32bhVoKSwvGy+Ul78IuAhGCqOPNDvGjJbo+AzRkFEq5TAn7 7oymFo/8IZ9gatkeWZkM2/l3Fj/TIYjivCTkaO6AW2HnEoOpMB+rRLB3gLz19yaTDJMu BEaA== X-Gm-Message-State: AOJu0YzzyztrvqxbVx6Bwb+xR1THUUNrDYZj4JyhuEJWxu8nlnPerDkd uIGAcjw6DoQ6Bz6N019gukzTf2Ej2vu2lbDpct13AoMni5avpzGQRQVaGcJqVWRpLuBm1VGFYc3 ri0G613ETCmI5zABxct5KQ8wKmbGNe3hX X-Google-Smtp-Source: AGHT+IG33cYYBEaao/U4k8qd2Sl4C3J3ujFFDNh2SIfGi1vMpWAe49L4vqtSheLhyLQZGulGUn8o0yzPBWNoEVm92DY= X-Received: by 2002:a05:6820:1a0d:b0:5c4:e8d:58be with SMTP id 006d021491bc7-5da98896595mr13048336eaf.3.1724121957308; Mon, 19 Aug 2024 19:45:57 -0700 (PDT) MIME-Version: 1.0 References: <61c36bcd640f421eae98cfdee06214ce@bcv.ch> In-Reply-To: From: Ron Johnson Date: Mon, 19 Aug 2024 22:45:46 -0400 Message-ID: Subject: Re: Containerizing PostgreSQL To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000d0a1e80620146cf9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d0a1e80620146cf9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Aug 19, 2024 at 9:34=E2=80=AFPM Bruce Momjian wr= ote: > On Mon, Jul 22, 2024 at 06:01:46AM +0000, Cainzos Yvan wrote: > > Dear All, > > > > > > > > What is your experience with containerizing PostgreSQL, particularly on > > OpenShift? > > > > I am looking to identify the advantages and disadvantages of this type = of > > architecture, mainly from an operational standpoint. > > > > I am interested in preferred use cases and those to be avoided. > > > > Thank you for sharing your experience. > > This presentation might be helpful, and its videos: > > https://momjian.us/main/presentations/administration.html#cloud > > https://www.youtube.com/watch?v=3DwKJBpcoRAsc#t=3D1h26m46s The important bits start here, I think. Distilled: 1. Do you have an existing VM infrastructure, like VMware? 2a. Do you *frequently* create new PG instances? 2b. Do you have *hundreds* of PG instances? For me, the answers are "yes" and "no,no". I've got a "design document" and common config files in a shared directory. Need a new PG server? I give a standard list of mount points and port numbers to the VM build team, and they come back with a server that has RHEL installed, and ports open. "yum install" a set of RPMs from PGDG. Five minutes later, I sudo to postgres, cp config file templates and run some sed commands. Up comes PG! Patching happens every three months; yum and bash scripts which I've developed over time make that pretty darned fast and painless. Thus, PG containers are of no use *to us*. Lots of application containers, but that's outside my domain. --=20 Death to America, and butter sauce. Iraq lobster! --000000000000d0a1e80620146cf9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Aug 19, 2024 at 9:34=E2=80=AFPM B= ruce Momjian <bruce@momjian.us&g= t; wrote:
On Mon, Jul 22, 2024 at 06:01:46AM +0000, Cainzos Yvan= wrote:
> Dear All,
>
>=C2=A0
>
> What is your experience with containerizing PostgreSQL, particularly o= n
> OpenShift?
>
> I am looking to identify the advantages and disadvantages of this type= of
> architecture, mainly from an operational standpoint.
>
> I am interested in preferred use cases and those to be avoided.
>
> Thank you for sharing your experience.

This presentation might be helpful, and its videos:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://m= omjian.us/main/presentations/administration.html#cloud



The important bits start = here, I think.

Distilled:
1. Do you have= an existing VM infrastructure, like VMware?
2a. Do you freque= ntly create new PG instances?
2b. Do you have hundreds= =C2=A0of PG instances?

For me, the answers are &qu= ot;yes" and "no,no".

I've= got a "design document" and common config files in a shared dire= ctory.=C2=A0 Need a new PG server?=C2=A0 I give a standard list of mount po= ints and port numbers to the VM build team, and they come back with a serve= r that has RHEL installed, and ports open.=C2=A0 "yum install" a = set of RPMs from PGDG.=C2=A0 Five minutes later, I sudo to postgres, cp con= fig file templates and run some sed commands.=C2=A0 Up comes PG!
=
Patching happens every three months; yum and bash scripts wh= ich I've developed over time make that pretty darned fast and painless.=

Thus, PG containers are of no use to us.= =C2=A0 Lots of application containers, but that's outside my domain.

--
Death to America, a= nd butter sauce.
Iraq lobster!
--000000000000d0a1e80620146cf9--