From: Laurenz Albe <laurenz.albe@cybertec.at>
To: KK CHN <kkchn.in@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: WAL Replication query
Date: Tue, 01 Nov 2022 07:41:11 +0100
Message-ID: <88faef33e966796226022d6e7f3e32ad6c59fcfd.camel@cybertec.at> (raw)
In-Reply-To: <CAKgGyB-SMT0RxeoifAfjkRx6RHEOgpn7sf8F_zD1DPsKydTu=w@mail.gmail.com>
References: <CAKgGyB-SMT0RxeoifAfjkRx6RHEOgpn7sf8F_zD1DPsKydTu=w@mail.gmail.com>
On Tue, 2022-11-01 at 11:25 +0530, KK CHN wrote:
> I am trying WAL replication,the setup is working with a primary and Standby server.
>
> Query is : When the primary crashes due an unforeseen reason,
> what may happen to the uncommitted transactions at primary ?
Their effects remain invisible.
> Those won't replicate to the standby right ?
They may be replicated, but their effects will remain invisible there too.
> How much data loss occurs in this case ?
Data loss? I don't understand. There is no data loss with replication.
If an incomplete transaction is rolled back, that is no data loss.
> What is the mechanism to overcome this uncommitted transaction loss due to primary
> server crash which is not replicated to the standby server ?
I don't understand. Are you perhaps talking about failover?
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, kkchn.in@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: WAL Replication query
In-Reply-To: <88faef33e966796226022d6e7f3e32ad6c59fcfd.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox