Re: vacuum on streaming replication

From: Chris Travers <chris(dot)travers(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>, Alex Samad <alex(at)samad(dot)com(dot)au>
Subject: Re: vacuum on streaming replication
Date: 2017-07-31 08:11:52
Message-ID: CAKt_Zfvjpb2JYSGuq5Uuu=OAkGxnZZjq6GoYD149nvudsPsyww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jul 31, 2017 at 10:08 AM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com
> wrote:

> On Mon, Jul 31, 2017 at 7:28 AM, Andreas Kretschmer
> <andreas(at)a-kretschmer(dot)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(at)postgresql(dot)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.
http://www.efficito.com/learn_more

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alex Samad 2017-07-31 08:59:38 Re: vacuum on streaming replication
Previous Message Michael Paquier 2017-07-31 08:08:50 Re: vacuum on streaming replication