| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | chandan Kumar <chandan(dot)issyoga(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Review my steps for rollback to restore point |
| Date: | 2025-03-07 13:45:12 |
| Message-ID: | CAKAnmmKKYE8Re21ukcBdOfS5iVgOb5uyOJWAgGG8JbV7hZu-ww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Mar 6, 2025 at 6:49 AM chandan Kumar <chandan(dot)issyoga(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mark bradley | 2025-03-07 14:34:49 | Re: Duplicate Key Values |
| Previous Message | Greg Sabino Mullane | 2025-03-07 13:24:57 | Re: [EXTERNAL] Re: Asking for OK for a nasty trick to resolve PG CVE-2025-1094 i |