Re: [ADMIN] Big sized materialized views break replication
| От | Lazaro Garcia |
|---|---|
| Тема | Re: [ADMIN] Big sized materialized views break replication |
| Дата | |
| Msg-id | 001501d28c21$d2ad0710$78071530$@gmail.com обсуждение исходный текст |
| Ответ на | Re: [ADMIN] Big sized materialized views break replication (Κοκμάδης Δημήτριος <dkokmadis@gmail.com>) |
| Список | pgsql-admin |
If recovery.conf has this configuration parameter:
primary_slot_name = repmgr_slot_1
The replication use replication slots otherwise when wal_keep_segments is reached, the redo logs are rotated.
With replication slot you only have the required wal files but with wal_keep_segments you only has the amount especified in it.
If you do not use replication slots there is no need of creating slots, see SELECT * from pg_replication_slots; on the master.
When a slot is used, wal_keep_segments has no effects and could be 0.
Regards.
De: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] En nombre de ???µ?d?? ??µ?t????
Enviado el: martes, 21 de febrero de 2017 08:23 a. m.
Para: pgsql-admin@postgresql.org
Asunto: Re: [ADMIN] Big sized materialized views break replication
Hello,
Is it possible to use replication with slots and without them in the same setup or it could cause a problem?
Regards,
Dimitris
В списке pgsql-admin по дате отправления: