Message-ID: <1965bf0f57744c2efcb23a0a7763d652254d05bf.camel@cybertec.at>
Subject: Re: Export operation efficiency in read replica
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Siraj G <tosiraj.g@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Date: Thu, 20 Mar 2025 17:03:51 +0100
In-Reply-To: <CAC5iy60NgOv2nRYNwSh2n-Pj82eUjghgWjV2VCuQUABsAZ9uiw@mail.gmail.com>
References: 
	<CAC5iy60ZzcsxL1GKAdUdiqA7TFv_yQW3ZkN07VJM8J1Xkdk8Gg@mail.gmail.com>
	 <e5e1bd6610da84292deb7ba0a3196b66f0b1bef7.camel@cybertec.at>
	 <CAC5iy60NgOv2nRYNwSh2n-Pj82eUjghgWjV2VCuQUABsAZ9uiw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/1965bf0f57744c2efcb23a0a7763d652254d05bf.camel%40cybertec.at>
Precedence: bulk

On Thu, 2025-03-20 at 18:28 +0530, Siraj G wrote:
> As per my understanding coming to a proper conclusion wrt RPO with
> export operation is challenging. Eg., the export started at x and
> ended at z, the time stamp here for many data sets is different.
> Moreover, I do not think there is an incremental way available for export=
, correct?

You are talking about "pg_dump", right?
A dump is always consistent, no matter how long it takes.

But if you want to take a daily dump of a 1TB database, you
are doing something wrong.  You should change the requirements.

Yours,
Laurenz Albe