MIME-Version: 1.0
References: <CAHV6zV=XN-keoXn-Qi=vMBvfG5JGxjhdFKTksczizXSXC31fXg@mail.gmail.com>
 <ddda8f051bfe265e74d50f17dd8a4227211b9633.camel@cybertec.at>
 <CAHV6zV=TP=LYexUs8ZTmJxYeoX2HKJHmVPApgrc3WJfYb3niDA@mail.gmail.com>
 <CAKFQuwbeakn6f8Qo1nOked-unPjYd-_tkG38E0xmjwYpL=VLcg@mail.gmail.com>
 <CAHV6zV=G3od8Pa7XOH5dR6LUZQ2aoM__zyV-GMWrfyz=gufF9A@mail.gmail.com>
 <CAKFQuwbzEDV2e4yfSpr8SkLyxEmAk=WPn3uo3C2q+1xR5VymVA@mail.gmail.com>
 <CAHV6zVm73D1pMUqg50Nep3pSh+eP-aAsRyUwu8qXFzudKjZb+g@mail.gmail.com> <CAHV6zV=qjFSp6tnkbPoJiM9rKj+hkGryaOxGZw23JpokkJo7Sw@mail.gmail.com>
In-Reply-To: <CAHV6zV=qjFSp6tnkbPoJiM9rKj+hkGryaOxGZw23JpokkJo7Sw@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Fri, 7 Mar 2025 08:45:12 -0500
Message-ID: <CAKAnmmKKYE8Re21ukcBdOfS5iVgOb5uyOJWAgGG8JbV7hZu-ww@mail.gmail.com>
Subject: Re: Review my steps for rollback to restore point
To: chandan Kumar <chandan.issyoga@gmail.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, 
	"pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000019caae062fc0d7a8"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmKKYE8Re21ukcBdOfS5iVgOb5uyOJWAgGG8JbV7hZu-ww%40mail.gmail.com>
Precedence: bulk

--00000000000019caae062fc0d7a8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 6, 2025 at 6:49=E2=80=AFAM chandan Kumar <chandan.issyoga@gmail=
.com>
wrote:

> need any correction or advise.
>

Honestly, this all seems overly complex and fragile. I'm not sure what the
overall goal is, but if it's to have a general PITR solution, use
pgBackRest. If it's just to have a fall back method for a particular
change, an easier solution is to stop replication, apply changes, and
promote the replica if something goes wrong.

Either way, you should have a test system setup that you can try out your
steps on. If a step fails and you do not understand why, this list is a
great resource. Practice this a lot on test systems until it all becomes
second nature.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

--00000000000019caae062fc0d7a8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Mar 6, 2025 at 6:49=E2=80=AFAM ch=
andan Kumar &lt;<a href=3D"mailto:chandan.issyoga@gmail.com">chandan.issyog=
a@gmail.com</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_conta=
iner"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><d=
iv>need any correction or advise.</div></div></blockquote><div><br></div><d=
iv>Honestly, this all seems overly complex and fragile. I&#39;m not sure wh=
at the overall goal is, but if it&#39;s to have a general PITR solution, us=
e pgBackRest. If it&#39;s just to have a fall back method for a particular =
change, an easier=C2=A0solution is to stop replication, apply changes, and =
promote the replica if something goes wrong.</div><div><br></div><div>Eithe=
r way, you should have a test system setup that you can try out your steps =
on. If a step fails and you do not understand why, this list is a great res=
ource. Practice this a lot on test systems until it all becomes second natu=
re.</div><div>=C2=A0</div></div><div dir=3D"ltr" class=3D"gmail_signature">=
<div dir=3D"ltr"><div>Cheers,</div><div>Greg</div><div><br></div><div>--</d=
iv><div>Crunchy Data - <a href=3D"https://www.crunchydata.com" target=3D"_b=
lank">https://www.crunchydata.com</a></div><div>Enterprise Postgres Softwar=
e Products &amp; Tech Support</div><div><br></div></div></div></div>

--00000000000019caae062fc0d7a8--