Re: pg_dump's results have quite different size

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Kaijiang Chen <chenkaijiang(at)gmail(dot)com>
Cc: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: pg_dump's results have quite different size
Date: 2016-12-20 13:50:18
Message-ID: 20161220135018.GY18360@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Greetings,

* Kaijiang Chen (chenkaijiang(at)gmail(dot)com) wrote:
> After I enlarged the max_standby_streaming_delay, it works well for some
> days (I have to increase the max_standby_streaming_delay when data is
> bigger).
>
> Thank you all!
>
> A suggestion might be: pg_dump from the standby is frequently used in
> backup tasks; it'll be much better if we have some options to ensure the
> pg_dump to finish; for example, an option to temporary stop the
> replication? Or do we already have some approach?

If you don't want long-running transactions on the replica to be killed
then you can enable hot standby feedback, but you'll have to accept that
there may be additional bloat on the master then.

Another option might be to consider alternative backup methods, such as
using physical backup tools instead of pg_dump.

Thanks!

Stephen

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-12-20 14:47:05 Re: Crash with a CUBE query on 9.6
Previous Message Kaijiang Chen 2016-12-20 10:38:10 Re: pg_dump's results have quite different size