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 1sSHvg-005vRS-QA for pgsql-general@arkaria.postgresql.org; Fri, 12 Jul 2024 15:11:24 +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 1sSHvf-009FTM-0e for pgsql-general@arkaria.postgresql.org; Fri, 12 Jul 2024 15:11:23 +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 1sSHve-009FT0-Ls for pgsql-general@lists.postgresql.org; Fri, 12 Jul 2024 15:11:22 +0000 Received: from mail-yb1-xb30.google.com ([2607:f8b0:4864:20::b30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sSHvX-001ic5-U0 for pgsql-general@lists.postgresql.org; Fri, 12 Jul 2024 15:11:21 +0000 Received: by mail-yb1-xb30.google.com with SMTP id 3f1490d57ef6-e03d49ff259so1910181276.2 for ; Fri, 12 Jul 2024 08:11:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720797075; x=1721401875; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ATQ+x4F3/vZLy7Yb+VxJKPEXgXwwN9Zkv0QEgesSZug=; b=FaRZf9vOXXRKoC41uUYO9b6Ka5nA9FTg17IqaYa5Wfvnp3gOgWOl+rMJf14Sxf0jUy 2OwfXUrB8AfBL7MLMhMmBtc5ArBzd1v8RhE0nXsAJdarwdXZ6d66lONVtf1/n0hG+ZZc hKac2VOMJi+diAet4T9HBYxOajVXHucTJJXMJCVNzVryOuc3sqBf8YvHVUv6xjOl/otS ggaG28QlhJdK5k3srReIRahbRtR4bx7jX+jRnDSjM5e4WGN4SwkGg/pa1G9+Js9uAvWk 6JGZLnyFNCYjK6MSfcWqYH+nWHtn8lUxZeh4yjmWe7kWnjLcc47JOwWswi4I8rPkeoxo uahg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720797075; x=1721401875; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ATQ+x4F3/vZLy7Yb+VxJKPEXgXwwN9Zkv0QEgesSZug=; b=MEHIAzmHqjrI8QDL0++HpSV9WlBtbLF1w/MmrRaJJMBgrU7WzAZre6IV/FZOGyD/SW ARD5t/OdZtO0pJIMUkftvLBLO8jEI37MKlkr8q6/m+Zo2zrZNiL1l5ZxspXbFsrrWUS+ T2LxUWOjPII4eJprAKezvZcq/eLAvzNRvMDzm2/8h7saYMMg31TII6YjrahTXm5JW1UA Iqg8unrXkgIMS0py5LeEyVSTGJMkDqO/77DVlb7PO4IFL02TyozXOHEkfdFE06ABJy+K QiVmnT3htoBqdiKz2KqVX89MF0J7CWvodBeW91YVmMdYNfDfcalAh/rUEVoBAxbOGlcA naFQ== X-Gm-Message-State: AOJu0YxAwkGm9F5mNllpuMlpvEx4k5VDGv+fhAHmuNKx6T00hGW8b8BY Xkly9zeWqyEGvz/0KHzrKww0UsQzjHLO7kC5pHaku7anaFbuNNHRoU8Ca3HRzsg7SH21eRgbUPk /1uXYuszu1Lb9j9rWOKlsy38uSDbhnMFRk8w= X-Google-Smtp-Source: AGHT+IET4IqMzdJgWhou2GOzJHxgGGJNSYIJ/SLiCIMehXAUdKIDmevTEQe7PQQI6e+SF9P0w8rdEapqrQkrdoANeJE= X-Received: by 2002:a25:b305:0:b0:dff:338e:4f6 with SMTP id 3f1490d57ef6-e041b043028mr12850979276.5.1720797074282; Fri, 12 Jul 2024 08:11:14 -0700 (PDT) MIME-Version: 1.0 From: Mukesh Tanuku Date: Fri, 12 Jul 2024 20:41:03 +0530 Message-ID: Subject: Replication lag in Postgres To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000057f7fa061d0e4a06" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000057f7fa061d0e4a06 Content-Type: text/plain; charset="UTF-8" Hello everyone. Firstly thanks to the community members who are addressing all the queries that are posted. Those give us more insights about the issues/doubts in the postgres. I have a question with postgres HA setup. We are setting up a 2 node postgres cluster with async streaming replication, we want to define a RPO (Recovery point objective) in case of primary failure. How can we best define the RPO in this setup? since it's an async streaming replication setup there might be a chance of data loss which is proportional to the replication delay. Is there any way we can configure the delay duration, like for example to make sure every 10 mins the standby sync has to happen with primary? Thank you Regards Mukesh T --00000000000057f7fa061d0e4a06 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello everyone.=C2=A0
Firstly thanks to the community = members=C2=A0who are addressing all the queries that are posted. Those give= us more insights=C2=A0about the issues/doubts in the postgres.=C2=A0
=

I have a question with postgres HA setup.
We are sett= ing up a 2 node postgres cluster with async streaming replication, we want = to define a RPO (Recovery point objective) in case of primary failure.=C2= =A0

How can we best define=C2=A0the RPO in this se= tup? since it's an async streaming replication setup there might be a c= hance of data loss which is proportional to the replication delay.=C2=A0

Is there any way we can configure=C2=A0the delay dur= ation, like for example to make sure every 10 mins the standby sync has to = happen with primary?=C2=A0

Thank you
Reg= ards=C2=A0
Mukesh T

--00000000000057f7fa061d0e4a06--