Re: Big sized materialized views break replication

From: Samed YILDIRIM <samed(at)reddoc(dot)net>
To: Κοκμάδης Δημήτριος <dkokmadis(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Big sized materialized views break replication
Date: 2017-02-01 11:08:07
Message-ID: 962741485947287@web7h.yandex.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

<div>Hi Dimitri,</div><div> </div><div>Could you please share Postgres installation version?</div><div>Also what do you mean by saying recreate materialized view, refresh or drop/create?</div><div> </div><div>Best regards.</div><div> </div><div>İyi çalışmalar.</div><div>Samed YILDIRIM</div><div> </div><div> </div><div> </div><div>01.02.2017, 12:41, "Κοκμάδης Δημήτριος" &lt;dkokmadis(at)gmail(dot)com&gt;:</div><blockquote type="cite"><div>Hello,<div> </div><div>I use hot standby replication mode. </div><div>When I try to recreate big sized materialised views, about 3G size, the replication breaks and I have to resync it. </div><div> </div><div>Is there any way to avoid it?</div><div> </div><div>My master server settings</div><div> </div><div><div>shared_buffers = 30GB</div><div>work_mem = 3146kB</div><div>maintenance_work_mem = 2GB</div><div>dynamic_shared_memory_type = posix<span style="white-space:pre;"> </span># the default is the first option</div><div>wal_level = hot_standby</div><div>wal_buffers = 16MB</div><div>checkpoint_segments = 128</div><div>checkpoint_completion_target = 0.9</div><div>max_wal_senders = 128</div><div>wal_keep_segments = 8</div><div>effective_cache_size = 90GB</div><div>default_statistics_target = 100</div><div>logging_collector = on<span style="white-space:pre;"> </span># Enable capturing of stderr and csvlog</div><div>log_directory = '/var/log/postgresql'<span style="white-space:pre;"> </span># directory where log files are written,</div><div>log_filename = 'postgresql-%Y-%m-%d.log'<span style="white-space:pre;"> </span># log file name pattern,</div><div>log_rotation_age = 1d<span style="white-space:pre;"> </span># Automatic rotation of logfiles will</div><div>log_min_duration_statement = 3000<span style="white-space:pre;"> </span># -1 is disabled, 0 logs all statements</div><div>log_line_prefix = '%t  '<span style="white-space:pre;"> </span># special values:</div><div>log_timezone = 'localtime'</div><div>stats_temp_directory = '/var/run/postgresql/9.4-main.pg_stat_tmp'</div><div>autovacuum = on<span style="white-space:pre;"> </span># Enable autovacuum subprocess?  'on'</div><div>log_autovacuum_min_duration = -1<span style="white-space:pre;"> </span># -1 disables, 0 logs all actions and</div><div>autovacuum_max_workers = 3<span style="white-space:pre;"> </span># max number of autovacuum subprocesses</div><div>autovacuum_naptime = 15min<span style="white-space:pre;"> </span># time between autovacuum runs</div><div>autovacuum_vacuum_threshold = 50<span style="white-space:pre;"> </span># min number of row updates before</div><div>autovacuum_analyze_threshold = 50<span style="white-space:pre;"> </span># min number of row updates before</div><div> </div></div><div> </div><div>Regards,</div><div>Dimitris</div></div></blockquote>

Attachment Content-Type Size
unknown_filename text/html 2.8 KB

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Achilleas Mantzios 2017-02-01 11:49:27 Re: Big sized materialized views break replication
Previous Message Achilleas Mantzios 2017-02-01 11:02:40 Re: Big sized materialized views break replication