Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pDDaG-0003bf-KF for pgsql-general@arkaria.postgresql.org; Wed, 04 Jan 2023 23:54:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pDDaE-00010B-Mc for pgsql-general@arkaria.postgresql.org; Wed, 04 Jan 2023 23:54:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pDDaE-0000u9-9h for pgsql-general@lists.postgresql.org; Wed, 04 Jan 2023 23:54:10 +0000 Received: from mail-pj1-x1034.google.com ([2607:f8b0:4864:20::1034]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pDDaB-0005zY-L0 for pgsql-general@lists.postgresql.org; Wed, 04 Jan 2023 23:54:09 +0000 Received: by mail-pj1-x1034.google.com with SMTP id v23so38088086pju.3 for ; Wed, 04 Jan 2023 15:54:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=Fhk5dCvnldxr2F2Y/EcqJjRZCuc1lnbYZP1FmTYMk+s=; b=fJYcb/e5yu2w3UiP98wNyuYPLmwt0+ZryGGAJ/Ex0SAB9jc1BIOKaAfrj+Ggy86rXM Ec4uf3TowQ7PJz3Adn1HMRT64YGFv7UR7aslwZvhMx50P5SuFZgmdUwXfXjDqHJCONxh 15h6Y2LeQCycVt0W73/KuzCd32Gl1yy/h21iZyellC20JD1Rz6QnL1lGUq+gU0/s74Zh nzNXLOoyBN+v9KcbrxxL+25TD7sow6frie0W3nJBujjxSqxtF4wRwLZ//Ch76ZTQI2FE 1m6C4I6on+2bAlzzBveTY5kZFw7M3tYpSLZQ+T1HR8nCVQVR+7iBpywlEYc2N81Xm5X1 LEng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=Fhk5dCvnldxr2F2Y/EcqJjRZCuc1lnbYZP1FmTYMk+s=; b=ozqT5bLkPa5WSFrSp2S0PjCOoh0MR2nlswdMKCQyC0Rjdr/M+WVYk4m+VNXqcI61hM Yu/2pqQjm5X5TNrCWTL2BjFeq8D42DCXHXDcWZ0c4GqXiOS7R4/PJtzzct2U3bYbLCgN pxlfH/hJdTUosFD545OlogMNM7uhFjp99fShRhlVgRKU39/M1MyrTA4h8aPOiXxW8eYD Y8jvpJrFXwL4vdgEWHlCc2qaDB42PofeCu8WlOI3bqoy3Y/B0d+wc0yHTZI+WUTWuM/0 X4CQN3XDvYm4Sn3dupm7zr5lGw0fNUoUQAr0pOrEsIZna+b2RFymS3A+Rf48VXnMqUvN u6Ag== X-Gm-Message-State: AFqh2koxDtDgbitzZP+rS8ecfR9hYNt6+k4ciQaIhQRMrm44d9rxskva qrOJm5OLb71DXqtTpuRcMS6KcCktUzA= X-Google-Smtp-Source: AMrXdXv3yX9qCFYmy7cSp25ysQOVcY1WtRxtLJoFCyUU+REHX9miu443ia1g+2Dco2nzqQRHmAnynA== X-Received: by 2002:a17:902:854b:b0:192:903c:3726 with SMTP id d11-20020a170902854b00b00192903c3726mr29274918plo.28.1672876445856; Wed, 04 Jan 2023 15:54:05 -0800 (PST) Received: from ?IPV6:2601:681:5a00:f790:7ecf:c123:4a13:a4a6? ([2601:681:5a00:f790:7ecf:c123:4a13:a4a6]) by smtp.gmail.com with ESMTPSA id q12-20020a17090311cc00b0018c990ce7fesm24848340plh.239.2023.01.04.15.54.04 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 04 Jan 2023 15:54:04 -0800 (PST) Content-Type: multipart/alternative; boundary="------------69Gxr0yw4lzZnfXbxYJP2woy" Message-ID: <547a49b4-c296-b82f-df34-11cc819d4336@gmail.com> Date: Wed, 4 Jan 2023 16:54:03 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: What is the best setup for distributed and fault-tolerant PG database? Content-Language: en-CA To: pgsql-general@lists.postgresql.org References: From: Rob Sargent In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------69Gxr0yw4lzZnfXbxYJP2woy Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 1/4/23 06:26, Age Apache wrote: > Dear PG experts, > > I am new to postgres, and I am also not a DBA. I am a solo developer > who is trying to evaluate what database to use for my hybrid > multi-tenancy sub-apps i.e. users of the application will be > authorised to use part or whole of the application based on their > authorisation levels. This delineation of user access has to also be > supported by the database, if possible. Also, for audit purposes the > data is append only. And the design is based on just two > tables(vertices and edges) to emulate a document-oriented(jsonb) graph > structure. > > Postgres is the database I am leaning towards for this project. But as > I am not a DBA and also a solo developer, I am trying to understand > how I can spend less time managing the DB and more time developing the > application. I would like to have a distributed and fault-tolerant DB > setup with multiple read and write nodes with little to no > configuration on my part, if possible. I am looking for a self-hosted > open source solution. > > Is this possible with PG? What is the best way to achieve this for a > non-DBA solo developer like me? > > Thanks and kind regards None of the experts chimed in so I ante up my $0.02. It won't be possible unless you become a serious DBA _and_ solo (full stack) developer.  Or you pay for db support. --------------69Gxr0yw4lzZnfXbxYJP2woy Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 1/4/23 06:26, Age Apache wrote:
Dear PG experts,

I am new to postgres, and I am also not a DBA. I am a solo developer who is trying to evaluate what database to use for my hybrid multi-tenancy sub-apps i.e. users of the application will be authorised to use part or whole of the application based on their authorisation levels. This delineation of user access has to also be supported by the database, if possible. Also, for audit purposes the data is append only. And the design is based on just two tables(vertices and edges) to emulate a document-oriented(jsonb) graph structure.

Postgres is the database I am leaning towards for this project. But as I am not a DBA and also a solo developer, I am trying to understand how I can spend less time managing the DB and more time developing the application. I would like to have a distributed and fault-tolerant DB setup with multiple read and write nodes with little to no configuration on my part, if possible. I am looking for a self-hosted open source solution.

Is this possible with PG? What is the best way to achieve this for a non-DBA solo developer like me?

Thanks and kind regards
None of the experts chimed in so I ante up my $0.02.

It won't be possible unless you become a serious DBA _and_ solo (full stack) developer.  Or you pay for db support.


--------------69Gxr0yw4lzZnfXbxYJP2woy--