Re: Why forcing Hot_standby_feedback to be enabled when creating a logical decoding slot on standby

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: sanyam jain <sanyamjain22(at)live(dot)in>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why forcing Hot_standby_feedback to be enabled when creating a logical decoding slot on standby
Date: 2017-06-12 06:52:06
Message-ID: CAB7nPqQYPJUy46i8VUYN2eK_f+Be_0dyghndc18jBuRT90Ro3w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 12, 2017 at 3:16 PM, sanyam jain <sanyamjain22(at)live(dot)in> wrote:
> I have created a logical decoding slot on a standby but i haven't enabled
> Hot_standby_feedback.What are the test cases where this setup will fail?

hot_standby_feedback needs to be enabled at all times in logical
decoding so as the node does not remove rows that are still needed for
the decoding, and a VACUUM passing by with a minimal xmin too high
would cause inconsistent decoded data.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-06-12 07:49:18 Re: A bug in mapping attributes in ATExecAttachPartition()
Previous Message Michael Paquier 2017-06-12 06:48:09 Re: ICU support on Windows