Re: Replication failed after stalling

On Mon, Dec 30, 2013 at 8:56 PM, Joe Van Dyk <joe(at)tanga(dot)com> wrote:
> On Mon, Dec 30, 2013 at 10:27 AM, Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> wrote:
>> On Mon, Dec 30, 2013 at 12:02 AM, Joe Van Dyk <joe(at)tanga(dot)com> wrote:
>> > On Sun, Dec 29, 2013 at 10:52 PM, Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
>> > wrote:
>> >> On Sun, Dec 29, 2013 at 9:56 PM, Joe Van Dyk <joe(at)tanga(dot)com> wrote:
>> >> > On Wed, Dec 18, 2013 at 3:39 PM, Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
>> >> > wrote:
>> >> > If I run "COPY (select * from complicate_view) to stdout" on the
>> >> > standby,
>> >> > I've noticed that sometimes halts replication updates to the slave.
>> >>
>> >> \x
>> >> select * from pg_stat_repication;
>>
>> And it would be very useful to take a look at your checkpoints and
>> replication configuration parameters on both master and replica.
>
> master and replica have same settings.
>
> checkpoint_completion_target: 0.9
> checkpoint_segments: 16
> checkpoint_timeout: 5m
> checkpoint_warning: 30s
> hot_standby: on
> hot_standby_feedback: on

I meant all the replication settings, see [1]. And pg_stat_statements
when there is a problem, preferable the error, because when everything
is okay it is not very useful actually.

[1] http://www.postgresql.org/docs/9.3/static/runtime-config-replication.html

--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA

http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray(dot)ru(at)gmail(dot)com