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 1sQ5oZ-007rKZ-Ox for pgsql-general@arkaria.postgresql.org; Sat, 06 Jul 2024 13:50:59 +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 1sQ5oY-003ffi-9F for pgsql-general@arkaria.postgresql.org; Sat, 06 Jul 2024 13:50:58 +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.94.2) (envelope-from ) id 1sQ5oX-003ffZ-US for pgsql-general@lists.postgresql.org; Sat, 06 Jul 2024 13:50:57 +0000 Received: from mail-lj1-x22b.google.com ([2a00:1450:4864:20::22b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sQ5oU-000ji4-Qy for pgsql-general@lists.postgresql.org; Sat, 06 Jul 2024 13:50:57 +0000 Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-2eaae2a6dc1so36742391fa.0 for ; Sat, 06 Jul 2024 06:50:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720273854; x=1720878654; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Eem6S4jvKBozFUwkJfAWsLzPDumyOAdMhe5Hc7LEcUk=; b=lsyleoaez4tYk8HwMlcH/Fb70d6pf3RgJhWL8Z5ZZ8BGIcYL9qqJAvZS6FKHjDT7o3 NDLCJzmsaGD5IHt1w2C/gX2RmctSAIQlcAfbDSiAkRCW5NSDHTymWOQvv12yOtJ9GBML YcELx+hSQieZmRqpAlyvCY1bvS8ddMTkny5Tuoe/9N9Now7fw4yAvbrLNVWQoRlg1PUj DZPsYsnFGgPDH7Xv/JVyx58rLTDv/Oj14pmdx+706lguuegdGSYi9icHE2KQNNRKa1K0 O3NxeU9tT4PZAEMSA4dACpsisHWgwrGsfgNrwqqbJDri7ksoCdyKoLQbp9j3tE8k9VAC 86Sw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720273854; x=1720878654; h=content-transfer-encoding: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=Eem6S4jvKBozFUwkJfAWsLzPDumyOAdMhe5Hc7LEcUk=; b=c1KQnIq+cYFU8W80AfoLvY6k6a7PFGgkPxzz9pUVBdWaZhNIsLrj9GjN5RA3YHNqX0 SrkoQAPe3lKxPd2bMRjZdpkwadwHDUIIutD5Nb0fctuOkYDmvgnfx5HTHCSSZCV2APvh tNV2w1FESaAeHG+4CzzrGJcGWA5i09UbV/monpQ41srVu7S2jQdNAEmc7NUQ0bHVlUqE MQdH4Zx584k8h98nN7iVGokWRDlsUnSf6StHP/y1oyIlRqbIckYqO4TO63sHgN+lhyL0 ubbNO6us556rZSUm+3xm2HH3UoOdINhZ3H90hX9Cn1+caLpF0vxOfVH1OYEw7s/tQ6rk i0dg== X-Gm-Message-State: AOJu0Yw/RegfIOOlZ23LR3rq73GIgVXDPCPjrNilX64RsQtWY1YHD7tJ hYMWbnr2GEgbl1EHNn/aNz1oivV6eRsVbUFX+g/SJGEuSwgi7pU2d//XutRHyHCU7LWcFh0MDWZ /oBUSZcoVjrdHHpiGK8cKuJp2/U4= X-Google-Smtp-Source: AGHT+IEt8DbHmgcaueX6hvugsHKmJwlErtSwEFVhTIlNmVGuYbhl2788wbn5YETRyDef66FzhLG9xthIyx0Hd8nJbss= X-Received: by 2002:a05:651c:2da:b0:2ee:849b:576a with SMTP id 38308e7fff4ca-2ee8ed69e04mr58986571fa.11.1720273852752; Sat, 06 Jul 2024 06:50:52 -0700 (PDT) MIME-Version: 1.0 References: <7644D22D-BFB3-4471-B077-30797AA838FC@lobeshare.co.za> In-Reply-To: <7644D22D-BFB3-4471-B077-30797AA838FC@lobeshare.co.za> From: Michael Nolan Date: Sat, 6 Jul 2024 08:50:42 -0500 Message-ID: Subject: Re: Alignment check To: Marthin Laubscher Cc: pgsql-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I don't have any direct experience with Yugabyte (the databases I work with are way too small to be on Yugabyte) but my older son does work for them as an SRE, sometimes remotely when he's visiting us, so we've talked about it a bit. (It's actually the first time in 20 years I've had much of a clue about what he's working with.) On Thu, Jun 27, 2024 at 11:08=E2=80=AFAM Marthin Laubscher wrote: > > Hi, > > I don=E2=80=99t intend dissing or plugging anyone=E2=80=99s efforts or st= art a flame war, but I=E2=80=99d like to get a sense of how the PostgreSQL = community feels about: > a) YugabyteDB, and > b) PostgreSQL on Kubernetes. > > For my application I=E2=80=99m deeply vested in Kubernetes as a pathway t= o being cloud-agnostic and I have looked at YugabyteDB because it matches m= y application=E2=80=99s (distributed) architecture more closely. > But not all the ways to run PostgreSQL on Kubernetes are created equal, a= nd YugabyteDB is really far behind on versions and do not support extension= s in a way that=E2=80=99s useful to me. > > So seeing that I=E2=80=99ve taken the plunge to join the mailing lists at= least I=E2=80=99d love to hear any and all feedback on those two topics fr= om the these parts of the woods. > > --- Thanks for your time =E2=80=93 Marthin Laubscher