Re: Can I skip function ResolveRecoveryConflictWithSnapshot if setting hot_standby_feedback=on all the time

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "funnyxj(dot)fxj" <funnyxj(dot)fxj(at)alibaba-inc(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Can I skip function ResolveRecoveryConflictWithSnapshot if setting hot_standby_feedback=on all the time
Date: 2018-11-20 15:57:08
Message-ID: CA+TgmoZ+wUW2a2_m788i22o_88jmPF2O1ysH8EmJk9om0GLNiQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 19, 2018 at 3:53 AM 范孝剑(康贤) <funnyxj(dot)fxj(at)alibaba-inc(dot)com> wrote:
> Hello,
> Can I skip function ResolveRecoveryConflictWithSnapshot if setting hot_standby_feedback=on all the time?
> As I know, function ResolveRecoveryConflictWithSnapshot is used for resolving conflicts once master cleans dead tuples. But if I set hot_standby_feedback to on, it will not appear conflicts, so I can skip to execute function ResolveRecoveryConflictWithSnapshot, am I right?

If I remember correctly, even with hot_standby_feedback=on, you could
still get conflicts if the connection between the master and the
standby is temporarily broken and then reestablished.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-11-20 16:17:30 Re: [RFC] Removing "magic" oids
Previous Message Alvaro Herrera 2018-11-20 15:50:42 Re: incorrect xlog.c coverage report