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 1tvd2d-006W6q-Hx for pgsql-general@arkaria.postgresql.org; Fri, 21 Mar 2025 14:08:07 +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 1tvd2c-0082jN-99 for pgsql-general@arkaria.postgresql.org; Fri, 21 Mar 2025 14:08:06 +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 1tvd2b-0082cK-V3 for pgsql-general@lists.postgresql.org; Fri, 21 Mar 2025 14:08:05 +0000 Received: from mail-ed1-x52e.google.com ([2a00:1450:4864:20::52e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tvd2W-000KbV-1C for pgsql-general@lists.postgresql.org; Fri, 21 Mar 2025 14:08:02 +0000 Received: by mail-ed1-x52e.google.com with SMTP id 4fb4d7f45d1cf-5e033c2f106so3003224a12.3 for ; Fri, 21 Mar 2025 07:08:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1742566079; x=1743170879; 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=hptvhFodgkBdMTNSW+D28AuNuYo4hxsryWWaTnvVoDM=; b=He80jUyx0xrcZSgToV0NqcBT53UbT++hmDt9/gyqcHSlDKAEEAkJpWEm6GOdlVIhaX 2udlluyIbpY+qGlx56qmMxAXC/268hmTXlZ8392VQ6jGqV+xBagEsEEmwQr9TWoBeLCA lfm7PPguHle5NQ8Mr8MwVGEbdXf9ccxfiWiOnnTVUoBlm6WBZv5bKC5MJeyhtmLldE/J wAB7IxPM4PvCNS/+Xuzn0Fylbi+zUeg3njo3+LN5A4fkpZZ9iOTkF4VPh6LMIuCQeK9t dpWs0kkYir4GXvbuH0cR242GZ5qmU0r1a2YHqLgmSwPJS5pBKOioCIkyqfpandaArcT4 YuNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742566079; x=1743170879; 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=hptvhFodgkBdMTNSW+D28AuNuYo4hxsryWWaTnvVoDM=; b=NXuyGmQdlnlkesGnunb2g3FkMHb58dnK36o5OhJHXvCGdRkEeIoK0mv4i2NiBIornV CG6RS0wViKNb/f5cxjlEADy1L1EI2D+KeXDL2PGmrRN9RzL6T1PfLKrJqPXKlkpK+prD Xz0qKLk3UyBZGvf7omkUAMAXG+gsprIrRFigsIqiJ4qKL0uVYYvoJOxQrTJhr//29ZMd yzYoEicbPTn/EYQwRJ25vvkC66sXkuPYUqtcsngaCmveveVQz5lwBI3Cr8PjZbswnlgJ u8uh+kNWnlSlIfjuKrEuGOJrt/tqA7RszJ4pG5KIczJha+sCdjKP/eN/F0AMv7Edwuf6 qrzA== X-Gm-Message-State: AOJu0YzLHBOrvFbe5FR89QJ7YstyOCCG9QNC9wA/ZqYe2UTVxTIVSy+L 6wsz+oGfMH/QVNb8o+GXKCV0ZbQEGVbDgt5k7/7uLhsVO5+9pSNrDMXSxJQjFWy4EHX0tAdZAYF WHVpEgxQhRCZiEE5DI0UR3qdlPHX0RDaA X-Gm-Gg: ASbGnctbx6Aht3sSAJ2olkDc9pyZLaP6MMAmJu0hUzDhVBv7PQPA3Tl8EYz4OYuu24c RwK8Iumm//Q8ribAy4xMiUAYKDM0Nt0A1j4J2zhp1dlEVtgJTQ3puGYOo2WO6Ru4e2hf9q2RwEI qHufFQZbr+h2aGJISU2MW8/pI/Pg== X-Google-Smtp-Source: AGHT+IH4i7QPCVVPOd76wCtvppNQ810flFXmFofkeZhuH3BTgnEcpUrEn3rzdehbf863xkqtOUDx+lKcXHoGUAlmxUc= X-Received: by 2002:a05:6402:1ecc:b0:5e4:92ca:34d0 with SMTP id 4fb4d7f45d1cf-5ebcd4fafcamr2976685a12.20.1742566079039; Fri, 21 Mar 2025 07:07:59 -0700 (PDT) MIME-Version: 1.0 References: <143af5f7-94c1-453b-803e-12f162780a83@aklaver.com> In-Reply-To: From: Siraj G Date: Fri, 21 Mar 2025 19:37:46 +0530 X-Gm-Features: AQ5f1JplsZBDjkO2t5ltnoCc4V2ctqGWBsHVx7WALkm2Xa4Icc94GP8CDOuqwMA Message-ID: Subject: Re: Export operation efficiency in read replica To: Guillaume Lelarge Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000239da30630dac888" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000239da30630dac888 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you everyone! On Fri, Mar 21, 2025 at 7:23=E2=80=AFPM Guillaume Lelarge < guillaume.lelarge@dalibo.com> wrote: > On 20/03/2025 15:04, Adrian Klaver wrote: > > On 3/20/25 05:58, Siraj G wrote: > >> Hello Laurenz > >> > >> As per my understanding coming to a proper conclusion wrt RPO > > > > You still have not defined what RPO is. > > > > I guess the OP is talking about Recovery Point Objective, which is one > of two important parameters WRT to disaster recovery. It's the maximum > data loss you agree on with your backup solution. That mostly depends on > the database context, something we can't tell. And according to how much > you agree to lose (one minute of activity? one hour?), you then can > choose between pg_dump or PITR backups. > > But with a 1TB-database, I wouldn't dare using pg_dump. PITR backup is > the only option. > > > -- > Guillaume Lelarge > Consultant > https://dalibo.com > > > --000000000000239da30630dac888 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you everyone!

On Fri, Mar 21, 2= 025 at 7:23=E2=80=AFPM Guillaume Lelarge <guillaume.lelarge@dalibo.com> wrote:
On 20/03/2025 15:04, Adrian K= laver wrote:
> On 3/20/25 05:58, Siraj G wrote:
>> Hello Laurenz
>>
>> As per my understanding coming to a proper conclusion wrt RPO
>
> You still have not defined what RPO is.
>

I guess the OP is talking about Recovery Point Objective, which is one
of two important parameters WRT to disaster recovery. It's the maximum =
data loss you agree on with your backup solution. That mostly depends on the database context, something we can't tell. And according to how muc= h
you agree to lose (one minute of activity? one hour?), you then can
choose between pg_dump or PITR backups.

But with a 1TB-database, I wouldn't dare using pg_dump. PITR backup is =
the only option.


--
Guillaume Lelarge
Consultant
https:/= /dalibo.com


--000000000000239da30630dac888--