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 1sTRG5-00GHDe-25 for pgsql-general@arkaria.postgresql.org; Mon, 15 Jul 2024 19:21:13 +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 1sTRG2-00Cd58-LZ for pgsql-general@arkaria.postgresql.org; Mon, 15 Jul 2024 19:21:10 +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 1sTRG2-00Cd4x-7N for pgsql-general@lists.postgresql.org; Mon, 15 Jul 2024 19:21:10 +0000 Received: from mail-qv1-xf36.google.com ([2607:f8b0:4864:20::f36]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sTRG0-002HlH-1C for pgsql-general@lists.postgresql.org; Mon, 15 Jul 2024 19:21:09 +0000 Received: by mail-qv1-xf36.google.com with SMTP id 6a1803df08f44-6b5db7936b3so28094156d6.1 for ; Mon, 15 Jul 2024 12:21:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721071266; x=1721676066; 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=oovpXF7FYK5RKIQfL5zG+W3lFZaQN54XpwnpYJBt+Yg=; b=ij1HUvs7HgreHIZzfSVbjqxD4P/M7NYMYsXhczFN9PBQdfvvBL3MWgpxzq8vzlrVl3 QD3sQBvdf6rB9bJQcPR4Cyo+asIZglZR24VXM39eYIPz4N5aZNdskknVpLLnlJpTgNtf KX+Y5rMLetN8/+pP3KTNrRyH3cakvVGxKQzWrwWNm6MbQJ/jamtNLFW4zxXOB+4QIHBx r/iAoOkoc4VGj86SfwBCpwuQl7XQvcNqBbbYPdYrtW0ChvLdeNob47V/S4espgxiEqyg KfssZXlrsRFxM0P7JkYzpzUMm6UQp5kc+8k+BzUSqMe5OosvzIALL1BPmHpsQqopplp6 7huQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721071266; x=1721676066; 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=oovpXF7FYK5RKIQfL5zG+W3lFZaQN54XpwnpYJBt+Yg=; b=A0i+JH2lSurGOZcfTe1SHw7IVog88ggVsx2DncD+E/FBeldJdLMQ5Tc9EfDo5efchG lwgaDZS+yGsbZBM0CRVZPQkbDav2x4RynTLEPg9bkcssSmdHuEA9bG7ImPTljog9kVJy I4QXQZalOBi7jdqwuz8RB/Ab5eBQEZ+B4hU7YzfcNhqOqm229RXb9X/v3SeaBLKyyMYF JCD/IFf2IV9/ep+gjr6MV3EYcAPD37jMthgHPzvOw64SUJlmIJhIXh3WxtufweQxqteI iiEGB3VkblpNis3hQoVH1joiT6wxcQyQkhNr88RFSkjyPN1mw4ptWanvobNweKFPiHmq KqJg== X-Gm-Message-State: AOJu0YzUL0426kUzb2SHpmicHZP5rBk15DMB4XUfkT53dOIZWya8n2NI ZmZhHqvNrd1LN0ByldIwT+NG0KA+oUtMF1eWzs6Rz64L90L/xf19IroUGDlkGiOWa/hKJ1D0OxX W58VNBzad5GordCYefpO1UdmRoSA= X-Google-Smtp-Source: AGHT+IEnQlGumHeNNOwT0l78zf/gxXADij7wyYsP6YjCCQnWLx6To+1/SjFo7ztlz0ENQ/6oAGW2yMNAaTToWT5l/os= X-Received: by 2002:a05:6214:19ed:b0:6b5:9fa:3224 with SMTP id 6a1803df08f44-6b77f4ee736mr2454396d6.13.1721071266084; Mon, 15 Jul 2024 12:21:06 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Mon, 15 Jul 2024 12:20:27 -0700 Message-ID: Subject: Re: PostgreSQL Active-Active Clustering To: "Sarkar, Subhadeep" Cc: "pgsql-general@lists.postgresql.org" , "Sur, Sanjay" Content-Type: multipart/alternative; boundary="00000000000072c3c3061d4e2183" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000072c3c3061d4e2183 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jul 15, 2024 at 12:06=E2=80=AFPM Sarkar, Subhadeep wrote: > > We are evaluating features of the Community edition of PostgreSQL in > relation to a proposal for a prospective client and need help with the > queries below:- > > > > - Does the Community edition of PostgreSQL provide NATIVE > active-active high availability clustering with objectives of scalabil= ity, > load balancing and high availability without using any extensions or > external components or usage of Kubernetes/Dockers. > > Basically, no. See "logical replication" if you'd like to delve into why I qualified this one. > > - In the Community edition of PostgreSQL is it possible to setup a > database cluster in load balancing mode and provide vertical and horiz= ontal > scalability without repartitioning or changes to the database objects = or > 3rd party transaction routing mechanisms using NATIVE features only (i= .e. > without using any extensions or external components or usage of > Kubernetes/Dockers). > > No > - In the Community edition of PostgreSQL is it possible to setup a > cluster where all the nodes are able to concurrently read-write the > underlying database image using NATIVE features (i.e. without using an= y > extensions or external components or usage of Kubernetes/Dockers). > > > No There is only one server process per underlying data directory in PostgreSQL. David J. --00000000000072c3c3061d4e2183 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Jul 15, 2024 at 12:06=E2=80=AFPM Sarkar, Subhadeep= <subhadeepsarkar@kpmg.com> wrote:


We are evaluating features of the Community edition = of PostgreSQL in relation to a proposal for a prospective client and need h= elp with the queries below:-

=C2=A0

  • Does the Community edition of PostgreSQL provide NATIVE active-active hi= gh availability clustering with objectives of scalability, load balancing a= nd high availability without using any extensions or external components or usage of Kubernetes/Dockers.
    • =
  • In the Community edition of PostgreSQL is it possible to setup a databas= e cluster in load balancing mode and provide vertical and horizontal scalab= ility without repartitioning or changes to the database objects or 3rd party transaction routing mechanisms using = NATIVE features only (i.e. without using any extensions or external compone= nts or usage of Kubernetes/Dockers).

No

--00000000000072c3c3061d4e2183--