Re: [GENERAL] vacuum on streaming replication

2017-07-31 Thread Alex Samad 
Thanks

On 31 July 2017 at 18:11, Chris Travers  wrote:

>
>
> On Mon, Jul 31, 2017 at 10:08 AM, Michael Paquier <
> michael.paqu...@gmail.com> wrote:
>
>> On Mon, Jul 31, 2017 at 7:28 AM, Andreas Kretschmer
>>  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.
> http://www.efficito.com/learn_more
>

Re: [GENERAL] vacuum on streaming replication

2017-07-31 Thread Chris Travers 
On Mon, Jul 31, 2017 at 10:08 AM, Michael Paquier  wrote:

> On Mon, Jul 31, 2017 at 7:28 AM, Andreas Kretschmer
>  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.
http://www.efficito.com/learn_more

Re: [GENERAL] vacuum on streaming replication

2017-07-31 Thread Michael Paquier 
On Mon, Jul 31, 2017 at 7:28 AM, Andreas Kretschmer
 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.
-- 
Michael


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

Re: [GENERAL] vacuum on streaming replication

2017-07-30 Thread Andreas Kretschmer 
On 31 July 2017 04:15:33 GMT+02:00, Alex Samad  wrote:
>Hi
>
>setup a cluster, with streaming replication and hot stand by
>
>the idea is to use the stand by to do queries whilst the primary is
>doing
>inserts.
>
>But I noticed the stats on the stand by server don't update, nor can I
>run
>vacuum against it as its in recovery mode.
>
>So how do update the stats and how will it affect my queries ?


The standby is read only, vacuum runs on the master and replicated to the 
standby. Analyse as well.

Regards, Andreas

-- 
2ndQuadrant - The PostgreSQL Support Company


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

[GENERAL] vacuum on streaming replication

2017-07-30 Thread Alex Samad 
Hi

setup a cluster, with streaming replication and hot stand by

the idea is to use the stand by to do queries whilst the primary is doing
inserts.

But I noticed the stats on the stand by server don't update, nor can I run
vacuum against it as its in recovery mode.

So how do update the stats and how will it affect my queries ?