Re: [GENERAL] vacuum on streaming replication - Mailing list pgsql-general

From Chris Travers
Subject Re: [GENERAL] vacuum on streaming replication
Date
Msg-id CAKt_Zfvjpb2JYSGuq5Uuu=OAkGxnZZjq6GoYD149nvudsPsyww@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] vacuum on streaming replication  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [GENERAL] vacuum on streaming replication  (Alex Samad <alex@samad.com.au>)
List pgsql-general


On Mon, Jul 31, 2017 at 10:08 AM, Michael Paquier <michael.paquier@gmail.com> wrote:
On Mon, Jul 31, 2017 at 7:28 AM, Andreas Kretschmer
<andreas@a-kretschmer.de> wrote:
> The standby is read only, vacuum runs on the master and replicated to the standby. Analyse as well.

Please note as well that if hot_standby_feedback is enabled, the
cleanup done by VACUUM on the primary is influenced as well so as
tuples that a standby may need to avoid conflicts for its transactions
are not removed. So VACUUM may result in less cleanup depending on the
read load on the standby.

Also that replication slots provide standby feedback and may further delay vacuuming when the standby is offline. 
--
Michael


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



--
Best Wishes,
Chris Travers

Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No vendor lock-in.

pgsql-general by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [GENERAL] vacuum on streaming replication
Next
From: Alex Samad
Date:
Subject: Re: [GENERAL] vacuum on streaming replication