| From: | sanyam jain <sanyamjain22(at)live(dot)in> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| 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-16 06:31:03 |
| Message-ID: | BM1PR01MB1011CDA3F7607F96EA932706C0C10@BM1PR01MB1011.INDPRD01.PROD.OUTLOOK.COM |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Isn't XLogRecord carries full information to be decoded in itself?If so a VACCUM should not be a problem in decoding?
Thanks
Sanyam Jain
________________________________
From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Sent: Monday, June 12, 2017 6:52:06 AM
To: sanyam jain
Cc: Pg Hackers
Subject: Re: [HACKERS] Why forcing Hot_standby_feedback to be enabled when creating a logical decoding slot on standby
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2017-06-16 06:45:46 | Re: proposal psql \gdesc |
| Previous Message | Andrew Borodin | 2017-06-16 06:24:03 | Re: GiST API Adancement |